Data corruption

  • Thread starter Thread starter Underpaid_Clerk
  • Start date Start date
U

Underpaid_Clerk

HELP all you wizards out there!

Have been running (ha - more like trying to run!) a
shared Access 2000 database on a unix-based Samba
server. Have had NUMEROUS strange errors, such as tables
disappearing, primary keys unsetting themselves, lost
data, numbers being misread, etc. Pulled database off
server, repaired and had no more problems, but was
instructed by the IT guy (backed by my boss) to leave the
database on the server. I ain't no rocket scientist, but
I experimented with running the dbase on the server and
on a local share. Every time it went to the server,
PROBLEMS! Now the whole thing is a mess, and I can't
balance any of my financial data.

Could running on the server for the last year have
totally corrupted the database? Nobody believes me, but
I've ruled out everything else! Help me save my sanity
and my job!

Thanks guys!
 
Underpaid_Clerk said:
Have been running (ha - more like trying to run!) a
shared Access 2000 database on a unix-based Samba
server. Have had NUMEROUS strange errors, such as tables
disappearing, primary keys unsetting themselves, lost
data, numbers being misread, etc.
Click to expand...

All signs of corruptions.
Pulled database off
server, repaired and had no more problems, but was
instructed by the IT guy (backed by my boss) to leave the
database on the server. I ain't no rocket scientist, but
I experimented with running the dbase on the server and
on a local share. Every time it went to the server,
PROBLEMS! Now the whole thing is a mess, and I can't
balance any of my financial data.

Could running on the server for the last year have
totally corrupted the database? Nobody believes me, but
I've ruled out everything else! Help me save my sanity
and my job!
Click to expand...

Yes, Samba can be responsible for corruptions. But it's not
necessarily Samba's fault..

Jet, the database engine underneath Access, uses something called
phantom locking using the .ldb file and does other wierdnesses.
There are papers discussing these nitty gritty details of the bowels
of Access.

The problem is that Samba isn't always a perfect implementation of
Microsoft's networking protocols. And it's not Samba's fault as some
of these details are not documented or poorly documented. Some
versions of Samba I've seen mentioned in the newsgroups as working
just fine.

I would suggest reposting with the words "data corruption with Samba"
in the subject to see if you get more responses. I'd also suggest
searching groups.google.com and www.google.com using keywords such as
"access corruption samba" to see if you get any hits.

Thanks for reminding me of this issue. I'll add it to the Corruptions
FAQ at my website.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Underpaid_Clerk said:
Have been running (ha - more like trying to run!) a
shared Access 2000 database on a unix-based Samba
server. Have had NUMEROUS strange errors, such as tables
disappearing, primary keys unsetting themselves, lost
data, numbers being misread, etc.
Click to expand...

This problem with Samba could also be related with excessive, to
Access, caching on the client network software. For example see
Possible Network File Damage with Redirector Caching
http://support.microsoft.com/default.aspx?scid=kb;en-us;148367

Or with OpLocks settings. (Whatever it's called on Unix servers)
Slow Performance When You Access Files on Servers
http://support.microsoft.com/default.aspx?scid=kb;en-us;301952

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top