keep getting corrupted records "12:00:00 AM "   

Hi all,

Last year we converted from A97 to A2000. We've had nothing but problems. 
Lately we keep getting corrupted records and I can't seem to narrow the 
problem down. We'll get "12:00:00 AM" in some of the date fields and the 
values from fields get shifted to the next field. Has anyone else had this 
problem? Or any ideas? Any help would be very much appreciated.

TIA
Ted

date: Fri, 14 Mar 2008 10:47:08 -0400   author:   Ted

Re: keep getting corrupted records "12:00:00 AM "   

On Fri, 14 Mar 2008 10:47:08 -0400, "Ted" 
wrote:

12AM sounds like you're looking at a field that has been formatted
(perhaps incorrectly) as "Time", and the time is 0, whereas you meant
"General Date" or some other format including the date..

Shifting values: sounds like a logic problem in the source code.
Access (better: Jet) doesn't just shift values around. Heck, they may
not even fit because the next field may be an incompatible data type.

-Tom.



>Hi all,
>
>Last year we converted from A97 to A2000. We've had nothing but problems. 
>Lately we keep getting corrupted records and I can't seem to narrow the 
>problem down. We'll get "12:00:00 AM" in some of the date fields and the 
>values from fields get shifted to the next field. Has anyone else had this 
>problem? Or any ideas? Any help would be very much appreciated.
>
>TIA
>Ted 
>
>

date: Fri, 14 Mar 2008 21:25:48 -0700   author:   Tom van Stiphout

Re: keep getting corrupted records "12:00:00 AM "   

A few things:

when access 2000 came out it had a tremendous amount of bugs, and problems. 
This means you must apply all the service packs and the updates to both 
office (access), and also install the updates to the jet database engine.

The next thing you need to ensure is are you talking about a multi user 
environments, and if yes, then you must split your database, and preferably 
distribute a mde to each WorkStation. While access 97 would "tolerate" a 
setup in which more than one user was in the front end at the same time, it 
generally was a bad idea. Later versions of access are far more sensitive to 
this issue, and will suffer from frequent corruption and damage to the code 
system if you don't install a copy on each WorkStation. (assuming we're 
talking about a multi user environment here).

I explain the concept of splitting here:
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

So in addition to splitting, try distributing a mde to each WorkStation.


-- 
Albert D. Kallal    (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

date: Sat, 15 Mar 2008 15:48:54 -0600   author:   Albert D. Kallal