Database corrupted

I hope someone can help me because I'm about to lose all faith in MS Access
as a development tool. I've always been plagued by corrupt databases. I work
at my office and I also telecommute and I always seem to get corrupt
databases the day after telecommuting even when the two access versions were
the same, reports were the worst problem. Now I have another corrupt database
after telecommuting. Our VPN gives us Access 2000 whereas I now use 2003 (in
2000 mode) at work, could this be the cause? The database will not open and
leaves a hanging LDB file. Can't open it with Jetcomp. Tried creating a new
database and importing all objects and it carries over the corruption. Anyone
got any ideas?

My experience (and the MS Knowledge Base confirms) that Access does not run
well over a WAN.

That said, you can improve your experience by starting with a split
database - each workstation with a separate front-end, linked to a common
backend database of the tables, located on your server/designated peer.

The LDB file should be deleted when every user has left the backend. You
can safely manually delete it, if your network has hiccupped and left a
phantom user.

If you can't fix MDB with the normal Compact & Repair and/or Jetcomp, then
the importing trick is one of the few remaining options. You'll need time
and/or luck to import everything BUT, the corrupt objects, then will need to
recreate any unrecoverable objects.

Check out: http://officerecovery.com/access/?submit/

Better yet, look at: http://www.granite.ab.ca/access/corruptmdbs.htm
for a consolidated list of what to do with corruption.
Good luck!
-Ed

"mscertified" wrote in message
...
I hope someone can help me because I'm about to lose all faith in MS Access
as a development tool. I've always been plagued by corrupt databases. I
work
at my office and I also telecommute and I always seem to get corrupt
databases the day after telecommuting even when the two access versions
were
the same, reports were the worst problem. Now I have another corrupt
database
after telecommuting. Our VPN gives us Access 2000 whereas I now use 2003
(in
2000 mode) at work, could this be the cause? The database will not open
and
leaves a hanging LDB file. Can't open it with Jetcomp. Tried creating a
new
database and importing all objects and it carries over the corruption.
Anyone
got any ideas?

Are you using your VPN as a file server only? Or do you use something like
Remote Desktop to actually work on your "work" machine? With the latter,
you may experience some lag in responsiveness, but you'll have less of the
corruption typical of a WAN.

"mscertified" wrote in message
...
I hope someone can help me because I'm about to lose all faith in MS
Access
as a development tool. I've always been plagued by corrupt databases. I
work
at my office and I also telecommute and I always seem to get corrupt
databases the day after telecommuting even when the two access versions
were
the same, reports were the worst problem. Now I have another corrupt
database
after telecommuting. Our VPN gives us Access 2000 whereas I now use 2003
(in
2000 mode) at work, could this be the cause? The database will not open
and
leaves a hanging LDB file. Can't open it with Jetcomp. Tried creating a
new
database and importing all objects and it carries over the corruption.
Anyone
got any ideas?