Date/Time field

[VolkHavaar]

Hello,

we're using Access 2007 linked with ODBC to a Mysql server.
I created a connection to a table called 'planning' and run queries on that table. In that table are several columns (int, varchar, datetime,..)

Now, we use this on several computers, all without issues. However one user has the following issue:
when she selects a column with the datetime type, Access freezes for about 3 to 5 seconds, and then displays the calendar date picker. For every date/time column, this only happens the first time a field is selected in that column, or after a change is made in that column.

So if columns B and D are of the type date/time, when a field is selected in column B, it hangs for about 5 seconds. After that, fields in column B can be selected normally. If a field is column D is selected, the same. We can then selects fields in both columns normally. If a field in a column is changed, the next time a field is selected in that column, the process restarts.

Apart from this, the table and query datasheet act normally, updates can be done, etc...just the short freezes on the date/time fields.

I've checked the ODBC settings and the regional settings on the computer, and the settings are the same as the other machines. We're using mysql-connector-odbc 5.1.5.

Has anyone experienced something like this, or has any idea where to start looking?

Kind regards,
Geert

[rpeare]

is the person experiencing the pause using a different version of access? even though the database may be access 2007, if your 'problem' user is using 2010 or 2013 there may be some issues with versions that would cause this delay. For instance, when I open a 2003 database at work on my 2007 machine I always experience delays when I'm using a particular reference in my coding. The only way I can get that delay to go away is to update the reference to the 2007 version, however, in doing so I create an invalid reference for the 2003 users.

If this is your situation the only way I've found to handle it is to give the newer version people a separate front end that is using the new version's references.

[VolkHavaar]

No, sadly, we're all using Access 2007. And when I open the *.mdb file on another machine, the problem isn't visible.
It looks like a client config issue, but other than changing Access versions and ODBC drivers, both of which I tried, I can't think of what would be causing this.

Luckily, it's not a super issue, as the user is able to work, albeit somewhat annoying

[rpeare]

Did you try uninstalling Access, shutting down, then reinstalling it to default conditions? That's the only other thing I can think to try if all the machines are equal.

Maybe check what version of the MS service packs they are on as well.

[VolkHavaar]

Thanks for the input...I might end up reinstalling the whole machine when our user is on holiday, that ought to sort it out