[AccessD] Network issues PLEASE ADVISE

Sander,

This sounds like what happens when the BE has moved. And, regarding Windows XP, are you running Service Pack 2?

Do you have a link-checking routine running at the start of your application like Tribble's AutoLinker? I had to modify one of the procedures in that library to avoid the incredible amount of time it would take for a link to be checked that was broken.

Regards,

Steve Erbach
Neenah, WI

"I belong to no organized party. I am a Democrat." - Will Rogers


> ------------Original Message------------
> From: S D <accessd667 at yahoo.com>
> To: accessd at databaseadvisors.com
> Date: Mon, Nov-1-2004 8:49 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