Jürgen Welz
jwelz at hotmail.com
Tue Jun 1 20:27:11 CDT 2004
I'm going to agree with the general approach as well. The only thing I do differently is use only one linked data source for each user and write a copy of the data file to the prelinked location. I was forced to use this approach because we could not create ODBC data sources but could reuse one that was made for our users. I found this approach fast and efficient and have adapted it for general use. As we had a multi user environment, each user had a standard file named with his user login and a linked table name that also contained his user name. For some types of datasources this is much faster than creating the link. Ciao Jürgen Welz Edmonton, Alberta jwelz at hotmail.com >From: "jwcolby" <jwcolby at colbyconsulting.com> > >Well.. Three out of three saying "that's what I did". I keep pretty >good company I guess. > >John W. Colby >www.ColbyConsulting.com > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock >Sent: Monday, May 31, 2004 1:13 PM >To: Access Developers discussion and problem solving >Subject: Re: [AccessD] Is there an easier way? > > >Hi John > > > Is my solution harder than it needs to be? Has anyone handled a > > situation like this and if so, how do you deal with it? > >Your approach sounds pretty much like I would handle this task ... > >You are, of course, looking for some shortcuts but I don't think there >will be any given the "dynamic" nature of the data formats. > >/gustav _________________________________________________________________ MSN Premium: Up to 11 personalized e-mail addresses and 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines