Charles, Mike makes a good point and you must consider multi user implications. However, that is the reason why I would probably use the table in the database. The same issues will apply if you write to an external file or to a table. I believe however, that there are a lot of options available to you with the table process. Built in record locking, time stamps easily implemented, last user to use the variable, last program to use the variable, the list could go on and on, depending on what all you wanted to record in the table. A "log" of the variable actions could automatically be kept for instance, by simply inserting a new row each time versus updating one row. The same could be done with an external file but if multiple users start writing to the same file name, you will run into some access violations. Putting them on different drives then poses the problem of which is the most recent.
If your goal is insure that any user is always using the latest value of a "Variable", the table method seems to be nice. If you want only a particular user to share a value, then writing a file to a local drive or using a user ID in the table would work as well. There are always many ways to accomplish something! Truthfully, not knowing more about why the question is asked, it is difficult to really present a good solution. I have never seen the need to pass a variable between sessions. I have seen the need to pass a "flag" or "Status" of something between databases, which is where ODBC comes in very nice. Perhaps if you could be more specific on why you need to pass a variable, it would help clear up the issue. -Bob Thompson Technology Consultants 276 Chippewa LaPorte, IN 46350 219-324-2605 (Phone & Fax) 219-363-7441 (Cell) http://ttc.inc.home.comcast.net -----Original Message----- From: MikeB [SMTP:[EMAIL PROTECTED] Sent: Friday, January 28, 2005 5:46 PM To: RBG7-L Mailing List Subject: [RBG7-L] - RE: Passing variables from one session to another > Create a table named VarHoldTab > Column 1 : VarName Text > Column 2 : VarValue Text (or whatever type your variable will be. Add columns for different types if needed) > If you are going to use the Database, It isn't going to be very multi user friendly without setting some Userid columns or something. Whatever variables are going to be saved between sessions surely are going to be different from one user to another. This is the reason I like to write them to files on the users local drive... Even so, if you Were still going to use the db, you don't have to do anything as complex as multiple column for different datatypes, you can just write the same info as my file example showed to Note Var and then save it in a VarChar data column, then retrieve it by using a Run Select...
