There appear to be several parts to this process:
1) Create the database. This part is easy.
You must have a license that allows creating a database, such as
ProVision. I used the Data Dictionary tool under the Procedure
Editor. I just created the database, then added tables to it and
then fields to the tables. If you've used temporary tables in a
progress application, you already have the definition of the
structure. If you've created tables in MS Access, the process is
about the same, but requires a lot more mouse clicks. I also added
descriptions, formats, labels, etc. to the fields, just like they
have in Vantage. I can then view this structure using my own version
of the Data Dictionary Viewer. (Similar to Vantage's screen of the
same name but with some useful enhancements).
I then connect to this database (in single user mode) and import
data into it. This step was mainly so I could test out my code using
a user-defined table (as opposed to a temp-table). It also works
with data from Vantage. I leave "MFGSYS" as the working database to
avoid confusion my code and refer to my database by name when I
access it.
Also, if you disconnect the MFGSYS database, or set any other
database to the Working Database while in a VB Form program, the
results could get ugly. (I once set the ProPath value to null by
accident in a VB form and Vantage crashed so hard the NTSB is still
looking for it's black box).
At this point, any ONE user can access the data, and it works well.
If two (or more) people need to access the database at the same
time, we must go to multi-user mode.
This is where it gets murky...
I attempted to add my database to the list using the progress
explorer tool. I got everything set up but it wouldn't start.
I also attached to open it using the data dictionary on the server
and it did not open.
It appears the database can't be moved, and must be accessed using
the same path it was created. (I created the database on client
workstation where the path is a mapped drive letter) and when I
attempted to access it on the sever through the local drive letter
it complained about it.
Even if I create a database on the server, this freshly-created
database does not work, as it does not have a lock table.
So it seems I need a way to move my database from one
path/drive/computer to another (Pro Backup on my client workstation,
then restore on the server?). next I need a means to make it a multi-
user database (a utility to prep the database?) and finally, I need
to know how to tell the Progress Explorer about it and how to start
it up as a multi-user database.
Somewhere along the line, I also need to know how to change this
database once it's in operation.
1) Create the database. This part is easy.
You must have a license that allows creating a database, such as
ProVision. I used the Data Dictionary tool under the Procedure
Editor. I just created the database, then added tables to it and
then fields to the tables. If you've used temporary tables in a
progress application, you already have the definition of the
structure. If you've created tables in MS Access, the process is
about the same, but requires a lot more mouse clicks. I also added
descriptions, formats, labels, etc. to the fields, just like they
have in Vantage. I can then view this structure using my own version
of the Data Dictionary Viewer. (Similar to Vantage's screen of the
same name but with some useful enhancements).
I then connect to this database (in single user mode) and import
data into it. This step was mainly so I could test out my code using
a user-defined table (as opposed to a temp-table). It also works
with data from Vantage. I leave "MFGSYS" as the working database to
avoid confusion my code and refer to my database by name when I
access it.
Also, if you disconnect the MFGSYS database, or set any other
database to the Working Database while in a VB Form program, the
results could get ugly. (I once set the ProPath value to null by
accident in a VB form and Vantage crashed so hard the NTSB is still
looking for it's black box).
At this point, any ONE user can access the data, and it works well.
If two (or more) people need to access the database at the same
time, we must go to multi-user mode.
This is where it gets murky...
I attempted to add my database to the list using the progress
explorer tool. I got everything set up but it wouldn't start.
I also attached to open it using the data dictionary on the server
and it did not open.
It appears the database can't be moved, and must be accessed using
the same path it was created. (I created the database on client
workstation where the path is a mapped drive letter) and when I
attempted to access it on the sever through the local drive letter
it complained about it.
Even if I create a database on the server, this freshly-created
database does not work, as it does not have a lock table.
So it seems I need a way to move my database from one
path/drive/computer to another (Pro Backup on my client workstation,
then restore on the server?). next I need a means to make it a multi-
user database (a utility to prep the database?) and finally, I need
to know how to tell the Progress Explorer about it and how to start
it up as a multi-user database.
Somewhere along the line, I also need to know how to change this
database once it's in operation.