corrupted write flag

B

bicyclops

Check out this line from Microsoft Article 283849:

"For more information about how to do this, see the "How to determine which
users/workstations are causing the file to be marked suspect" section later
in this article. "

It's referring to being able to figure out who has caused the Write Flag to
be marked suspect for corruption. I'm very interested in this info, but the
section that it mentions doesn't exist in this article or any other that I
could find. Anyone ever hear of this capability? (I already know how to see
who is logged in.)

Thanks.
 
R

Rick B

Are you using a Microsoft Access database? This newsgroup is for questions
about Microsoft Access, the database product.
 
B

bicyclops

Most definitely using Access. The article I refer to below is called: How to
troubleshoot and to repair a damaged Access 2002 or later database.
 
B

bicyclops

Maybe so. I'm familiar with that article. But it doesn't have any methods to
figure out which user has corrupted the database. The statement in 283849
says there is a way to see who has marked the write flag as suspect.

This information would be extremely valuable. Our database is getting
corrupted about 2x per week. It would be great to know if primarily one
workstation is responsible.
 
V

Van T. Dinh

Look in the equivalent article for Access 2000, i.e. KBID = 209137 and you
see the section you are looking for.
 
B

bicyclops

Thanks. Looks like nothing further is availalbe than what I have already. I
appreciate the follow-through. I'm surprised a text search didn't yield the
same results in the knowledge base for me.
 
T

Tony Toews

bicyclops said:
Check out this line from Microsoft Article 283849:

"For more information about how to do this, see the "How to determine which
users/workstations are causing the file to be marked suspect" section later
in this article. "

It's referring to being able to figure out who has caused the Write Flag to
be marked suspect for corruption. I'm very interested in this info, but the
section that it mentions doesn't exist in this article or any other that I
could find. Anyone ever hear of this capability? (I already know how to see
who is logged in.)
Click to expand...

This is interesting. I don't ever recall seeing any mention anywhere
of exactly what you are looking for. That is the network userid or
network ID or some other unique identifier of the machine who has
corrupted the database. As far as I know this simply isn't available
anywhere.

What is available, as you already are aware, is who is logged onto the
MDB. But this is obtained from the LDB locking file. The corrupt
flag is inside the MDB file.

I'm going to forward your posting to Microsoft however I suspect their
response will be to remove the phrases and sentences that you have
mentioned.

Do note that Microsoft really, really likes the feedback that you can
give any KB articles or web pages. They won't necessarily agree with
you but they will read those comments. So I'd suggest clicking the
appropriate check boxes and entering your comments as you have typed
them for us.

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
 
T

Tony Toews

bicyclops said:
This information would be extremely valuable. Our database is getting
corrupted about 2x per week. It would be great to know if primarily one
workstation is responsible.
Click to expand...

To track when people logged in and out as well as abnormal
terminations I did the following.

In one situation I created some logic behind a hidden form which was
opened when the database was opened. It added a record to a logging
table containing relevant info such as NT userid, work station name
and so on. The autonumber ID of this record was retained on the form.
When the database was closed, which meant this form was closed, the
form then updated that record, using the stored autonumber ID as
having normally terminated.

We could then monitor users who were having problems or were using
abnormal methods of closing Access. Kinda funny to visit a user and
state "I see you were having a problem yesterday. What was happening?"
They'd look a bit surprised and then tell you. We never had to worry
about someone doing the Ctrl+Alt+Del or hitting the power switch as it
was an all NT4 network and they were good users.

I get my information which I log from the workstation name and the NT
logon user name. See the API calls at the Access Web at
www.mvps.org/access. I haven't bothered to use Access security yet.

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

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
 
B

bicyclops

Tony- Thanks very much for your insight.


Tony Toews said:
This is interesting. I don't ever recall seeing any mention anywhere
of exactly what you are looking for. That is the network userid or
network ID or some other unique identifier of the machine who has
corrupted the database. As far as I know this simply isn't available
anywhere.

What is available, as you already are aware, is who is logged onto the
MDB. But this is obtained from the LDB locking file. The corrupt
flag is inside the MDB file.

I'm going to forward your posting to Microsoft however I suspect their
response will be to remove the phrases and sentences that you have
mentioned.

Do note that Microsoft really, really likes the feedback that you can
give any KB articles or web pages. They won't necessarily agree with
you but they will read those comments. So I'd suggest clicking the
appropriate check boxes and entering your comments as you have typed
them for us.

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
Click to expand...
 
T

Tony Toews

bicyclops said:
Tony- Thanks very much for your insight.
Click to expand...

The folks at Microsoft are looking into this. Please check that
article on a regular basis. It may take a while though. A while
may be a week or a month or more.

Once you do see a change please send me an email at tony at granite
dot ab dot ca.

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
 
T

Tony Toews

The folks at Microsoft are looking into this. Please check that
article on a regular basis. It may take a while though. A while
may be a week or a month or more.
Click to expand...

And no guarantees of course. They may decide to rewrite the article
and remove than tantalizing hint. <smile>

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
 
Top