petermeachem
Programmer
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.
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?
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.
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?