Hi Keith
First up, close Access, and make sure there is no ldb file in the same
folder as your mdb. The ldb contains locking information. Access normally
deletes it, but if the computer/application crashes, you can be left with
spurious locking info that has to be deleted manually.
If that does not solve the problem, try creating a new, blank, A97 database
(File | New) in A97, and then import all the objects from the damaged one
(File | Get External | Import).
BTW, my ISP is having problems with their news server, so I'm not able to
get back for quick replies at present.
--
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.
"Keith Wilby" <keith.wilby@AwayWithYerCrap.com> wrote in message
news:Xns955874C3881D0keithwilby@10.15.188.42...[color=blue]
> "Allen Browne" <AllenBrowne@SeeSig.Invalid> wrote:
>[color=green]
>> This link contains our experience with upgrading Access.
>> It does not address the SQL Server aspects, but does describe
>> Setup, Conversion, and Usability issues:
>> Converting from Access 97 to 2000, 2002 or 2003
>> at:
>>
http://members.iinet.net.au/~allenbrowne/ser-48.html[/color]
>
> Allen,
>
> When I run the decompile routine on my A97 file I get an error telling me
> that the file is already in use (it isn't) and that the version of VBA
> used
> to create the code doesn't match what's on my PC. I've recently been
> given
> a new PC but it still has our 'standard' corporate image on it.
>
> I'm not sure where to go from here, any polite suggestions? :o)
>
> Regards,
> Keith.[/color]
