Access corruption - New Idea

[JamesSF]

Ok folks - anyone heard of this before?

I have a frontend/backend A2K running over a Citrix XP machine. 5 users.

When the 5th users logs in, the backend corrupts immediately. So i figure, a
bad NIC, right? Dropping a session and resetting the db connection. Access
is sentitive to network hangups and burps.

so, i moved the user to another pc, soon as she logs in, bam - corrupts the
db.

it was the user profile. we rebuilt the user profile, no problems.

1) anyone heard of this?

2) what could be in the profile causing it? if i knew, would be faster to
fix that rebuilding profile

James SF

 

[Albert D. Kallal]

Ok folks - anyone heard of this before?

I have a frontend/backend A2K running over a Citrix XP machine. 5 users.

When the 5th users logs in, the backend corrupts immediately. So i figure, a
bad NIC

How could a bad nic affect this? You are using Citrix? Do you have any idea
of how, or even what Citrix is?

Ask your self if a bad NIC card on your computer can corrupt the
www.amazon.com book database? Imagine while you are ordering a book at
Amazon, and your computer has a bad NIC. I think you will being to realize
that this is not possible. You can pull the plug, or even blow up your
computer, but you will still NOT damage the database on www.amazon.com.

The same goes for Citrix. Citrix means that each computer NEVER touches the
data (just like the web). That being case, bad nics, or users destroying
their pc with a bomb will NOT damage, or corrupt the file. Of course, if you
are NOT using Citrix, then yes, most certainly resetting your computer,
pulling the plug, or a bad NIC card is OFTEN the reason.

However, with Citix, you pcs are not touching the data. Only mouse clicks
and screen updates travel down the wire (exactly like using a web browser).
Thus, in the case of Citrix, bad client computers or bad NICS can not hurt
the data.

Assuming that each user who logs on still gets THEIR OWN COPY OF THE FRONT
END, then I would look at the opp-locks problem.

Access
is sentitive to network hangups and burps.

Not when using Citix.

2) what could be in the profile causing it?

It is possible that each of your users are NOT getting their own front end
(so, your profile is logging causing each user to use the same front end on
the Citrix server). Rember, each user is STILL to get their own copy of the
front end, EVEN when using Citrix.

Further, you MUST MAKE CERTAIN that the admim of the system is NOT killing
users who do not log off correctly, and are still running ms-access. You
cannot kill active users while in ms-access. They must exit ms-access, and
log off correclty.

Assuming all of the above is ok, and good, then this sounds like a opp locks
problem.

There is mention of this problem at:

http://www.granite.ab.ca/access/corruptmdbs.htm