Hi -

We are using a database of appoximately 10 users with about 3000+ records.
For some reason every now and then I'll get a corrupted record. The record
pulls up with boxes and chinese looking characters. I checked all the users
MS Jet versions and everyone seems to be up to date. The only other thing i
can think of is some users are using MS Access 2002 and some are using MS
Access 2000. Can anyone shed some light?

Best Regards,

Kameron

Is the database split? If that is a new concept, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html

For further suggestions on preventing corruption, work through the list at:
http://allenbrowne.com/ser-25.html
A flakey network card is a common cause.

The difference between the 2 versions could possibly cause a corruption of
the code, but what you describe sounds like a corruption of the data, so
that is unlikely to be worth pursuing. If you want to address the code
issue, make sure the users have MDE (not MDB) files, so it cannot decompile.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Kam" <(E-Mail Removed)> wrote in message
news:53B3A86A-1F82-498A-971E-(E-Mail Removed)...
>
> We are using a database of appoximately 10 users with about 3000+ records.
> For some reason every now and then I'll get a corrupted record. The
> record
> pulls up with boxes and chinese looking characters. I checked all the
> users
> MS Jet versions and everyone seems to be up to date. The only other thing
> i
> can think of is some users are using MS Access 2002 and some are using MS
> Access 2000. Can anyone shed some light?
>
> Best Regards,
>
> Kameron

Yes. The database has been split since development. Everyone has their own
FE file on their desktops.

"Allen Browne" wrote:

> Is the database split? If that is a new concept, see:
> Split your MDB file into data and application
> at:
> http://allenbrowne.com/ser-01.html
>
> For further suggestions on preventing corruption, work through the list at:
> http://allenbrowne.com/ser-25.html
> A flakey network card is a common cause.
>
> The difference between the 2 versions could possibly cause a corruption of
> the code, but what you describe sounds like a corruption of the data, so
> that is unlikely to be worth pursuing. If you want to address the code
> issue, make sure the users have MDE (not MDB) files, so it cannot decompile.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Kam" <(E-Mail Removed)> wrote in message
> news:53B3A86A-1F82-498A-971E-(E-Mail Removed)...
> >
> > We are using a database of appoximately 10 users with about 3000+ records.
> > For some reason every now and then I'll get a corrupted record. The
> > record
> > pulls up with boxes and chinese looking characters. I checked all the
> > users
> > MS Jet versions and everyone seems to be up to date. The only other thing
> > i
> > can think of is some users are using MS Access 2002 and some are using MS
> > Access 2000. Can anyone shed some light?
> >
> > Best Regards,
> >
> > Kameron
>
>
>