Thanks Dan.

I've settled my file management and "path" issues for now using non-cleared
global variables to switch focus.

1.  Storing everything within the database sounds great. Right now, my
coding is too all-go-to-heck to commit.

2.  The RBSYNC documentation introduces the prospect of 'individual RX files
in separate folders':

"... Encoding the timestamp in each of the four database files enables the
database files to be stored in separate directories apart from one another.
... "

Performance rewards, maybe? Store the massive BLOB CAD library on a separate
disc, thereby allowing virtual concurrency in RX2,RX3 and RX4 file access?





-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Dan Goldberg
Sent: Monday, July 15, 2013 6:39 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: File Management Question

I have no code files outside the database. The only things I have in the
folder is the RX files, compiled EXE's( or external form files),  and the
CFG file.

I am not sure why you would want the have the individual RX files in
separate folders.

Dan Goldberg

-----Original Message-----
From: Bruce A. Chitiea
Sent: Friday, July 12, 2013 7:16 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - File Management Question



All:



Fishing for perspective for this single-user development environment.



With complexity, automation and backup issues in mind, assuming a dedicated
data partition and unlimited space, which of these two file management
structures might make the best long-term sense?



1.    Each individual database ( R:Atabase.RX* ) and all related code files
stored within its own dedicated folder path, or;

2.    All database files ( *.RX* ) stored within one folder, with separate
dedicated folder paths for related code files.



Or am I missing an option? (I understand that the individual .RX? files can
be distributed among folders, but I'm not there yet.)



Thanks for your thoughts,



Bruce Chitiea

SafeSectors, Inc.

eCondoMetrics

909.238.9012 Cell


Reply via email to