Susan Zeller
szeller at cce.umn.edu
Wed Feb 12 14:58:37 CST 2003
I'm sure there are several approaches, but I would have a table in SQL Server that stores user specific information such as tblMyUsers. Have a field for your user, ie MyUserName. Then have fields for whatever you need stored such as AcctNumberPart. You can use SQL Server to find out which user is connected at the moment (select system_user) and then use that to look up the appropriate values in your table. This solution is not machine specific, but user specific. It sounds like you are customizing the front end table for each user. If this is true, that seems tedious to me. A parallel option would be to store a custom form in each adp file with the info you need. You could have this form open to read the data you need. This seems like an inferior option to me, though. --Susan -----Original Message----- From: David Emerson [mailto:davide at dalyn.co.nz] Sent: Wednesday, February 12, 2003 2:35 PM To: dba-SQLServer at databaseadvisors.com Subject: [dba-SQLServer]Local Tables in an ADP I am working on an application which was upgraded from an A97 FE/BE to and AXP ADP/SQL2K. In the previous version we had some local tables in the FE that held information specific to that FE (and there were several FE's). For example when a new client was entered then their account number was generated partly from a number held in the local table. Different FE's had different number ranges for new accounts. My understanding is that there are no local tables in an ADP. What is the way around storing information on each machine that is specific to that machine? Regards David Emerson DALYN Software Ltd 25b Cunliffe St, Johnsonville Wellington, New Zealand Ph/Fax (877) 456-1205 _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com