C
chrisW
Hi
We have a very large (58 module), antiquated but mostly stable
application here that still runs on NT 3.51 using the access 2
runtime. Everything is fine, but since swapping to new hardware with
2.4ghz processors the now() function returns the wrong system time!
The time tends to be about 20 minutes out (in the future), then not
update until approximately the time it displays, then jumps forward 20
minutes again..
I have tried installing access 2 on a box and calling the function
directly, which gives me the incorrect time, replaced the processor
with a 1.8ghz chip and everything is then ok. I put the 2.4ghz chip
back in and it all goes wrong again.
Unfortunately my application is time critical, so all the 'deadlines'
within the application occur at the wrong time, making the application
useless - it seems to be very difficult to buy a new pc less than
2.0ghz at the moment.
I've searched the web and microsoft websites to no avail, so this is
my last hope, does anybody have any ideas?
Thanks
Chris
We have a very large (58 module), antiquated but mostly stable
application here that still runs on NT 3.51 using the access 2
runtime. Everything is fine, but since swapping to new hardware with
2.4ghz processors the now() function returns the wrong system time!
The time tends to be about 20 minutes out (in the future), then not
update until approximately the time it displays, then jumps forward 20
minutes again..
I have tried installing access 2 on a box and calling the function
directly, which gives me the incorrect time, replaced the processor
with a 1.8ghz chip and everything is then ok. I put the 2.4ghz chip
back in and it all goes wrong again.
Unfortunately my application is time critical, so all the 'deadlines'
within the application occur at the wrong time, making the application
useless - it seems to be very difficult to buy a new pc less than
2.0ghz at the moment.
I've searched the web and microsoft websites to no avail, so this is
my last hope, does anybody have any ideas?
Thanks
Chris