Don, Javier, Karen, Mike, Buddy:

Thanks for the excellent feedback.

Two big takeaways from your responses are:

1a.  Get the code into the database (ultimately), or:
1b. 
2.  Develop from scratch for multi-user (asap).

For now I've reorganized as follows:

D:\ACTIVE\ -- All active application data files contained within this root

D:\ACTIVE\RBASE\ -- All RBASE related databases and non-RBTI-program
resources.

...\RBASE\DBMS\ --Root contains ALL 'RBName*.RX*' files. No other files.

...\DBMS\0COMMON\ -- RMD code resources used by all databases, including
startup, backup, and database-switching files.

...\DBMS\RNAME1\ -- All development resources for database RNAME1
.
.
...\DBMS\RNAMEn\ -- All development resources for database RNAMEn

The Startup file takes full advantage of CHOOSE and non-cleared global
variables to establish PATHs, select the database name and code folder name
(one and the same), makes the code folder active and launches the database.

This makes it very easy to run backup routines horizontally or vertically
across the structure, both inside and outside of R:Base. At the R> prompt,
moving between database code sets is as simple as typing: 'CD ..\RNAMEn',
although I've automated that, too.

You guys are great, thanks again.

Bruce


Reply via email to