Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Slow to start 1

Status
Not open for further replies.

petermeachem

Programmer
Aug 26, 2000
2,270
GB
I asked this in the office forum, no response, so i thought i'd try the proper forum.
This is an Access 2003 programme saved as Access 2000 because some people had 2000 years back and i've never changed it.
This programme has been in use with about 50 users for years. Always has started very promptly. When I change it, a new copy gets copied to the users C drive, and they run it from there.
Now, when a new version is opened, it sits there with a white screen for around 2 minutes and then works fine. If it is closed and reopened, it starts as quickly as it used to.
The change that has been made is that we have a new accounts system, so it has some extra links to the accounts system sql server.
There are also links to other sql databases which have not caused this problem.
The difference, if this is relevant, is that the accounts sql odbc are using Sql Server authentication, the others are Windows NT authentication.
If I start a fresh copy with my finger on the shift key, it starts quickly. If I then double click on any linked table, whether from the new accounts or one of the old databases, it hangs for 2 minutes. On some, very few pc's, this problem doesn't show up. The pc's are mostly xp professional, a few Windows 7 professional.
This seems very weird. I haven't been able to find out why it does it or how to fix it. Anybody have a clue?
 
Is Autocorrect still turned on? Turn it off.. Tools, Options, General Tab, Right side of dialog uncheck Track Name Autocorrect Info.

My hunch is that Autocorrect is forcing a connection of all the tables which for some reason is slow... I'll leave the why to your DBA but this should speed up opening, but the first time you access a table on the problem SQL server it will be slow.

Then again, I might not be right.
 
This is a shot in the dark but... Are your ODBC sources set up under System DSN or User DSN? For some reason, I changed some from System to User and a system loaded a lot faster. I've not investigated why. I assumed that they were the same for the current user.
 
They are System. They all are, the older ones have always been System and that hasn't caused any problems.
 
If you create a new Access file and link a table to each database, does one take a suspicioulsy long time to open?

I am just trying to establish if it is an ODBC / Network / Authentication issue or something else.

If something else, you might try linking tables to a new file and then inmport objects until it slows down... Then you can start looking at that object for problems.
 
Yes you are right, i need to take a systematic approach to this. We have changed to a new accounts system, there is a huge amount of changes to make and nobody bothered to plan anything or take any notice of people saying, Gosh there is a lot of work here. Although the users are annoyed, they will have to remain so for a while. I've a credit reference company export file to recode by Thursday. Hopefully on Friday I can look at this in detail.
Thanks for your help, I'll report back if I find anything
 
I saw this thread...
thread701-1637724

While I don't expect it is useful, it did get me to thinking.

Try linking a single table in a differnt database and open a table with it... Then open the second database.

My hunch is things are timing out authenticating on the Server. If this makes things works, I would bet that is the issue... In which case I would want to fix the server ideally, or play with the timing settings under Tools, Options, Advanced Tab, Lower Left hand corner...

I mean is the SQL server a Domain Controller? Any reason it can't or shouldn't be? - If authentication is local to the server, it should go faster. Another thought, do the Servers have a backbone link so as not to compete with clients and properly configured to use the backlink? - I mean if this is the issue, making the Server a DC might only lead to timining problems replicating the domain.

If I find another kitchen sink, I'll post it too.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top