paul.hartland at fsmail.net
paul.hartland at fsmail.net
Wed Oct 29 02:50:49 CST 2003
How I have done something similar before is whichever table I need information to be remembered, I add an extra field (say MyLastRec, usually Integer). Every user that I allow access to the system will have a UserID. So when the user goes back into the system, it picks up their UserID, looks into whichever table they were in last and displays the record(s). If there is no reference that they had previously been on a record, then start as normal. Paul Hartland Message date : Oct 29 2003, 03:47 AM >From : David Emerson To : dba-SQLServer at databaseadvisors.com Copy to : Subject : [dba-SQLServer]Linking to Local Table AXP adp, SQL2000 Currently I have a table of customer primary keys that is filled in from the contents of a list box. This table is then used to link to other tables as a filter for processing client records. Because the BE is in SQL, the same table is accessed by all users. However, a user often wants the selection to be maintained between sessions (ie if they return to the selection screen the next day they want their previous day's selection still showing.) This excludes temporary tables (I think) because the users close the program over night. If there was a table stored on the local drives then each user could have their own list of customers. What I am unsure of is how I can a) link to the local database to fill it up with the selections, and b) how I can reference that table within SQL sprocs which use sql tables. Any pointers/key words to look up? Regards David Emerson Dalyn Software Ltd 25 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