[AccessD] Access Error

No, I didn't know about this William. And, although I've heard y'all
talk about Rocky's solution, in the past, I have never done it, so I
couldn't remember how it was done. As luck would have it, I am in the
middle of an office move, so my books weren't close at hand either.

I thank you guys for your help. As usual...I know I always say this...I
could count on this list for help. Unfortunately...for me anyhow,
because I wanted to play w/this...they did not wait for me and got it
from a backup. Actually, one of the techs, who happens to be in charge
of our backups, heard me and his supervisor talking and went out and
grabbed it. That is good I guess, but I wanted to actually try this
technique out. And, yes, they already deleted the "bad" file.

Thanks again!

>>> wdhindman at bellsouth.net 11/3/2005 9:31 PM >>>
...did you try MS's Jet Compact tool? ...it has always worked for me
when 
nothing else would get me into a corrupted mdb 
...http://support.microsoft.com/kb/q295334/ ...hth :)

William

----- Original Message ----- 
From: "John Clark" <John.Clark at niagaracounty.com>
To: <accessd at databaseadvisors.com>
Sent: Thursday, November 03, 2005 4:01 PM
Subject: Re: [AccessD] Access Error


>I can't get into it at all...how do I do this?
>
> Actually, it isn't an emergency any longer. We grabbed it off of a
> backup tape, but I want to know for the next time.
>
>>>> bchacc at san.rr.com 11/3/2005 2:55 PM >>>
> John:
>
> I'd try:
>
> 1. Compact and repair
> 2. Decompile
>
> first.
>
> Rocky
>
> ----- Original Message ----- 
> From: "John Clark" <John.Clark at niagaracounty.com>
> To: <accessd at databaseadvisors.com>
> Sent: Thursday, November 03, 2005 11:43 AM
> Subject: [AccessD] Access Error
>
>
>> I've got a user that just called our office with an A2K problem.
>> Something happened w/the system and she had to reboot her PC, while
>> Acess was saving...this is according to her.
>>
>> The problem is that her db, which I am quessing is just basic
tables
>> and basic, if any, forms, will no longer open. The error that we
are
>> getting is, "The Microsoft Jet database engine stopped the process
>> because you and another user are attempting to change the same data
> at
>> the same time."
>>
>> Anybody got a clue how to get into this thing?
>>
>> I have tried:
>>
>> 1) Moving the db to another directory (Stupid, I know, but I was
> hoping
>> to clear any locks up that way...maybe it would see it as a whole
> new
>> instance)
>>
>> 2) Removing any "connected" open files...the ldb...there was a
> hidden
>> file that I believe was the ldb (I did it too quick to be
sure...but
>> there not usually hidden...right)
>>
>> 3) Renaming the file (I thought if it were looking at it, from a
>> network file usage this might trick it.
>>
>> I really don't know, and as you can tell, I am grasping here.
> Luckilly,
>> I haven't had very many problems since switching to Access, so I
> haven't
>> had too much experience with this. When we used FoxPro...still got
>> some...it broke everytime there was a network problem...plus some.
> I've
>> still got a version of "FoxFix" on my PC that I have to drag out,
> every
>> now and then.
>>
>> Thanks
>>
>> John W Clark
>>
>> -- 
>> AccessD mailing list
>> AccessD at databaseadvisors.com 
>> http://databaseadvisors.com/mailman/listinfo/accessd 
>> Website: http://www.databaseadvisors.com 
>>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd 
> Website: http://www.databaseadvisors.com 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd 
> Website: http://www.databaseadvisors.com 
> 


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