SQL Server/Access 2007 date field is slooooow! Why? 2

[Haikster]

I am working with a client to migrate an Access 2000 app to Access 2007. I went through the conversion process and everything runs great except anything having to do with date/time fields. The Access app is odbc-linked to a back-end SQL Server 2000 DB. Whenever a date field is clicked, the app appears to "hang" for about thirty seconds! This is driving me nuts! There is no event properties tied to the field. In fact, I can look at the table view and click on a date without even going through a form and it does the same thing. What the heck is it doing? How can I fix this? Any ideas?

 

[smain]

Have you found a solution yet? We are experiencing the same problem, but only on the form view.

 

[AlexCuse]

Are you using a bound form?

Can you post DDL for your SQL table (and what the date/time column is represented as in access maybe even?)

In the future, you might try this forum as it gets a bit more traffic: forum181

Good Luck,

Alex

Ignorance of certain subjects is a great part of wisdom

 

[Haikster]

Well...here is the latest:

We called Microsoft and they looked at our app remotely. They appeared to be as stumped as I was, but I suspect they had some more insight. Access 2007 appears to still be a bit bug-ridden. They suggested that I minimize the top ribbon during runtime and that actually worked! Although it solved the problem of the time field hanging; I think it is totally unacceptable that I would have to minimize the ribbon!!! What is it doing? This database has about 53,000 records. It is almost as if it attempts to rip through every record for some housekeeping function behind the scenes making it very slow when you enter a time field. Like it is attempting some sort of conversion or something. This is real weird. I am glad to hear that I am not the only one going nuts over this.

 

[smain]

Haikster - Thanks for the post. We minimized the ribbon and now the form works fine. Hopefully there will be a permanent fix for this type of problem.

 

[BobRodes]

You may not like Microsoft's greedy propensity for putting stuff out there before it's reliable, but you gotta love their support when you really need it. I once had them spend about 60 man hours fixing a problem for a client, and they charged $200. (An example of "really need it" would be to have a computer professional take all of the XP workstations out of one office, as well as the Win2000 server, move them down the road to an older office, remove the old NT server from the older office, plug the Win2000 server into the old NT backbone, and also plug all the XP boxes into same, turn everything on, and then make a discreet exit--graciously declining to charge for his services--when nothing worked. Microsoft made me look like a genius putting out that fire.)

 

[Databaseguy]

Wow, that's wierd. Thanks for the tip.

But yeah, I noticed it too and it was driving me nuts. I turned the date picker off, thinking that was the problem, but no.



The good news is anyone can create an Access database.

The BAD news is anyone can create an Access database.