[dba-SQLServer]Linking to Local Table

Martin,

Can you explain further please.

David

At 29/10/2003, you wrote:
>Bit out of the blue this but what about a local XML file.
>
>Martin
>
>
>
>
>----- Original Message -----
>From: "David Emerson" <davide at dalyn.co.nz>
>To: <dba-sqlserver at databaseadvisors.com>
>Sent: Wednesday, October 29, 2003 10:32 AM
>Subject: RE: [dba-SQLServer]Linking to Local Table
>
>
> > Thanks David,
> >
> > I think I might have a problem here with temp tables.  Because the people
> > who will be using the client list will be logged on as the same used, any
> > temp tables they create will have the same user name, therefore
>overwriting
> > themselves.
> >
> > Are you sure it is not possible to set up a connection with another data
> > source other than the main SQL BE?
> >
> > David
> >
> > At 29/10/2003, David wrote:
> > >You can always save the data to a .csv, .dat or .txt file.  I have also
> > >created a "temp db"  and exported my data into a table in that tempdb.
>when
> > >finsihed with it the whole mdb is killed. Unfortunatley you cant link the
> > >table in the temp db to the ADP as you could with an mdb, but you can
>still
> > >open, transfer and populate fields with ADO/DAO. I got the idea from a
> > >sample database on Roger Carlsons website
> >
> >(http://rogersaccesslibrary.com/download2k.asp?SampleName='ImportToTempData
>b
> > >ase2k.mdb'). He created the sample to avoid bloat when using temp tables
>in
> > >mdbs. If you need more help with pulling exporting/importing data from
>the
> > >temp db I do I can send you.
> > >
> > >
> > >HTH
> > >David McAfee
> > >
> > >-----Original Message-----
> > >From: dba-sqlserver-bounces at databaseadvisors.com
> > >[mailto:dba-sqlserver-bounces at databaseadvisors.com]On Behalf Of David
> > >Emerson
> > >Sent: Tuesday, October 28, 2003 7:47 PM
> > >To: dba-SQLServer at databaseadvisors.com
> > >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
> >
> >
>
>_______________________________________________
>dba-SQLServer mailing list
>dba-SQLServer at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
>http://www.databaseadvisors.com