[AccessD] Database Corruption

We have had some problems when the filepath from the server perspective
is longer than 255 characters for the BE.

I.E you may access the BE via a share name (\\server\sharename\BE.mdb),
however  the REAL file path on the server may be something like
S:\databases for public use\department one\..\..\..\BE.MDB
When the BE.mdb path may actually be longer than 255 characters

Also check Microsoft for file locking issue with Windows XP non SP
workstations on Windows 2003 servers. You have said that this has only
been a problem since the SAN move, is the new SAN hosts 2003? And the
old server host was 2000?
If this is the case, file locking by the CLIENT is likely.

--andrew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer
Gross
Sent: Thursday, 1 December 2005 1:07 PM
To: AccessD List
Subject: [AccessD] Database Corruption

I have a multi-user (approximately 15 users) database split BE and FE,
with the FE residing on each individual work station or Terminal Server
in separate user directories.  About a week ago IT moved the BE to a SAN
and since then we have been experiencing corruption of the BE about 3
times a day.  I have imported all the tables and relationships into a
new database - still corrupting, rolled back the FE to one that was
stable prior to the corruptions starting - still corrupting, moved the
BE back to the server off the SAN - still corrupting and now I am going
to import the table structures into a new database and then import the
data into the new tables.

It is an A2K FE and BE.  Most users are on Win2K with A2K, some are on
WinXP with AXP or A2003.  Does anyone have any ideas what could be going
on here?  Any suggestions are appreciated.

Thanks in advance,

Jennifer Gross


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


This message and any attached files may contain information that is confidential and/or subject of legal privilege intended only for use by the intended recipient. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, be advised that you have received this message in error and that any dissemination, copying or use of this message or attachment is strictly forbidden, as is the disclosure of the information therein. If you have received this message in error please notify the sender immediately and delete the message.