Mark Breen
mark.breen at gmail.com
Mon Nov 1 10:07:32 CST 2004
Hello Sander, I wrote an email about this roughly a year ago to the list. This is a documented aspect of the combination of what happens when you upgrade your server to Windows 2K. It effects programmetic links to back end databases. It specifically effects the linked table connection. There were two ways that I could see to fix it, 1) was to redesign my system so that I open a seperate db and provide programmatic accesss to the tables, this would eliminate the need to linked tables, they would become local tables that happened to the located on a different server, (local to the DAO object model that is). The second way to solve it was to just import the tables back into the front end and not use a FE / BE model. I was reluctant to do this, however, when I presented the option to the client, she was happy enough to do this. That was a year ago and i have had no problems with it since. The 'feature' is clearly documented on the knowledge base and when I looked at it, MS had said that they had no intention to resolve this issue. You are welcome to see if that has changed. Best of luck with it. BTW, this issue did only effected databases with programmatic control of the linked tables. If you have a database (even a hugh one), that just connects uning linked forms etc, then you will have no problem. Best of luck with it, Mark Breen Ireland On Mon, 1 Nov 2004 07:47:51 -0800, Rocky Smolin - Beach Access Software <bchacc at san.rr.com> wrote: > Sander: > > What happens if you move the back end to a local machine, relink the tables? > Does it open fast? > > Also, are you relinking the tables on open every time? > > Rocky Smolin > Beach Access Software > http://www.e-z-mrp.com > > > > > ----- Original Message ----- > From: "S D" <accessd667 at yahoo.com> > To: <accessd at databaseadvisors.com> > Sent: Monday, November 01, 2004 6:24 AM > Subject: [AccessD] Network issues PLEASE ADVISE > > > Hi group, > > > > I've got a MAJOR problem. > > > > I've got an A2K application with a BE and a FE. FE is installed on the > > local machine and the BE is installed on the server. Using WinNT > > Performance has always been soso. Not fast but not very slow either. > > > > Now we've migrated everything to A2k2 with WinXP. > > > > Performance is terrible times 10!! Opening the FE takes about 20-25 > > minutes. Opening a linked table takes 9 minutes same goes for tables in > > the FE itself. > > > > However, when I open the FE and if I open a table that is stored in the FE > > it opens directly, no problem. When I then open a linked table => bang > > back to 9 minutes per table (linked or not) > > > > Is it possible that this somehow has to do with A2k2?? I know in Access 2 > > (that is two!!) you had to change OPENFILES parameter thingies somewhere. > > Does Access 2002 also have such a setting that must be tweaked?? > > > > TIA > > > > Sander > > > > > > --------------------------------- > > Do you Yahoo!? > > Yahoo! Mail Address AutoComplete - You start. We finish. > > -- > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >