Company Z (comp_z.dbc) File

Asked by: matbroughty 681 views Questions Back to Questions »

Good Morning,

I have connected via ODBC to the Fox Pro db (Pegasus Opera II) fine and have manged to work out the basic queries to extract the Sales and Purchase Ledger accounts and associated items (basically SNAME, STRAN for Sales Ledger and PNAME, PTRAN for Purchase Ledger).

Will the database container file always be called comp_z.dbc though or would the company letter change?  If it could be different what Pegasus installation files would indicate the name of the database container file?

The reason is I would like to be able to programmatically determine the data location.

I can determine the actual data directory location by viewing the Windows Registry entry in  HKLM\SOFTWARE\Pegasus\Server VFP\System and the PathToServerDynamic value, but there doesn’t appear to be an entry for the name of the database container file.

Registry Entries

So will it always be comp_z.dbc?  I’m guessing not!

Additionally does anyone know if the Pegasus Opera III Fox Pro databse is pretty much the same schema as II?  Likewise does the SQL server version stick to the same database table names/schema in general as the FoxPro version.

Thanks for any help anyone can offer.

Cheers

Mat

3 Answers



  1. Brian on Jul 08, 2011 reply

    Hi Mat, and welcome to the forum.

    The name of the database container file will change according to the Opera company ID. COMP_Z.DBC is for Company Z which is Opera’s demo data company.

    The data locations can be found in SEQCO which can be found in Opera’s System folder. As I am sure you are aware, it is important to be careful when opening up Opera’s database to avoid causing damage.

    For the main tables, such as the ones you identified above, Opera 3′s schema is pretty much identical to Opera II’s. At least for now; this may change as new features are added to Opera 3.

    The VFP data schema is applicable for SQL with the following additional fields per table – datecreated, datemodified, state (this field is to denote the VFP state of whether a record is marked for deletion or not). Also, if the corresponding VFP table does not have an ID field then the SQL one will.

    Hope this helps.

    Brian

    0 Votes Thumb up 0 Votes Thumb down 0 Votes



    • matbroughty on Jul 08, 2011 reply

      Hello Brian,

      Thanks enormously for the response. It really is appreciated.

      Yes it looks like the SEQCO table has the information I need to be able to automatically determine the database container (or containers if multi company).

      So the System Visual Fox Pro database containing the SEQCO table is also used even if the core database utilised by Pegasus is actually SQL Server?

      I probably need to get hold of Opera III VFP and SQL Server versions somehow – may look into the Pegasus developer programme, although I think they want Visual FoxPro skills which our company doesn’t use (Java shop) and all I\we want to do really is directly query the database through an ODBC\JDBC source.

      Thanks again.

      0 Votes Thumb up 0 Votes Thumb down 0 Votes



  2. Brian on Jul 08, 2011 reply

    “So the System Visual Fox Pro database containing the SEQCO table is also used even if the core database utilised by Pegasus is actually SQL Server?”

    I know that this was the case when the SQL version first came out, but I’m not sure whether it still is. I would say that it’s likely though.

    0 Votes Thumb up 0 Votes Thumb down 0 Votes


Answer Question

Notify me of followup comments via e-mail. You can also subscribe without commenting.