Darren DICK
d.dick at uws.edu.au
Thu Jul 15 21:46:24 CDT 2004
HI Stuart Thanks for this I have read and re-read the blurb from M$ I still don't get it. I have set the permissions on the TEMP folder on my DEV machine to anyone can do anything they like from anywhere withany logon :-)) Compiled - decompiled and compacted and repaired the DEV version of the back end whilst it was on my DEV machine Then I copy this local DEV version of the BE to the server - drop it into the expected place then try and perform some tasks and now I get Error 3260 "Could Not Update; currently locked by user '(unknown)' on machine " It isn't locked at all - like I said I have admin permission on the server. No-one else is looking at that file at all. The KB section of MS was useless. Any suggestions?? I'm starting to get desperate this will halt the deployment of the app due this Monday Many thanks Darren ----- Original Message ----- From: "Stuart McLachlan" <stuart at lexacorp.com.pg> To: "Access Developers discussion and problemsolving" <accessd at databaseadvisors.com> Sent: Friday, July 16, 2004 10:59 AM Subject: Re: [AccessD] A2K: Error 3343 When I install Backend on server > On 16 Jul 2004 at 10:40, Darren DICK wrote: > > > Hello all > > I have a FE/BE app setup. > > When I install the FE on my local DEV machine and put the BE in another > > directory on the same DEV machine - all is OK the app works fine > > > > BUT...When I put the BE on a server and put the FE on my local DEV machine and try to open the > > usual screens that work finer when it's all local I get the error msg > > > > Error 3343 - Unrecognised database format S:\Truman\Truman_Data\Truman_data.mdb > > > > The S: drive is a valid server drive only I have access to. I have Admin permission level i.e. full read and write permissions > > > > The data base MDB file is valid and is a recognised format - when I copy the MDB file in question from the server and place > > it on my local machine then connect my FE to - all is well. So it's most likely not the BE MDB file. > > > > Any suggestions? > > > > I'd guess you have done a Compact on the BE database. Took me a while to work > it out when I first came across this one :-( > > I finally found http://support.microsoft.com/default.aspx?scid=kb;EN-US;295234 > > "SYMPTOMS > After you compact a Microsoft Access database or an Access project that exists > in a folder in an NTFS file system partition, you may notice that the custom > NTFS permissions for the Access database file (.mdb) or for the Access project > file (.adp) are reset unexpectedly." > ...... > "CAUSE > The compact process always compacts the source Access database file or the > Access project file to a new file. The newly created file inherits NTFS > permissions that are different from the source file. The inheritance of the > NTFS permissions is based on the version of Access that is used to compact the > file." > > > > -- > Lexacorp Ltd > http://www.lexacorp.com.pg > Information Technology Consultancy, Software Development,System Support. > > > > -- > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com