Database Corruption - again

[Dave G]

One of me clients suffers regular corruption - sometimes the fields of
a record turn to chinese characters, sometimes a record will lose its
ID and all fields appear as ### 's.

I tried to tackle this some while ago but got nowhere. I felt it was
caused by filter-by-form, which I got rid of and the problem reduced a
lot, but didn't go away completely. Now it's happening more and more
and it's time to re-visit.

There are lots of tables and lots of forms but all the corruption
involves what one could call the main table and it's associated form.
It is a bound form. Something occurred today which made me think that
the problem may be linked to users scrolling through records. (This
user says a record corrupted as she arrived at it whilst scrolling
rapidly!! ). It's a very 'busy' form with approx 150 fields, lots of
drop downs getting their data from linked tables and worst of all a
photo which is pulled in from a share on a server and displayed in the
record.

It clearly takes a little time to display the record, so does anyone
think this problem could be related to the speed that users scroll up
and down the recordset ? I've asked them to scroll slowly for a while
and see if it has any effect.

For info, BE on a W2003 server, FE on workstations which are XP with
SP2 and each with 1MB ram. They never got this with A97 on W2000
workstations.

Any thoughts - this is driving me mad !!

Thanks
Dave

[Tim Marshall]

Dave G @ K2 wrote:

It clearly takes a little time to display the record, so does anyone
think this problem could be related to the speed that users scroll up
and down the recordset ? I've asked them to scroll slowly for a while
and see if it has any effect.

It is. I have this problem on A2K3 for images that are not embedded.
Scrolling too fast locks things up.

This is a solution offered by Steven Lebans on this group not too long
ago, here's the google link:

http://tinyurl.com/hmt7g

It's registry manipulation and therefore a bit scary to me and I was
instead thinking of trying to do something with the timer event, ie,
save the picture path to a variable, but not try to load until a couple
of seconds after and only if the picture path is the same at that
time... to avoid loading in response to every record scroll... I find
when I do this on one of my apps that uses a lot of pictures, the
database locks up.

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

[Stephen Lebans]

Tim that is an old post you are referring to. Here is a more current
version.

From: Stephen Lebans - view profile
Date: Sat, Apr 29 2006 1:59 am
Email: "Stephen Lebans"
<[e-mail]>
Groups: microsoft.public.access.reports
Not yet ratedRating:
show options
Here's a previous post of mine on this issue.

The one thing you must do is turn of the Loading Image dialog. If you don't,
and quickly scroll through the records in Form view, or page quickly in
Print Preview, you run the risk of crashing Access. Use the Registry mod at
the Access MVP site:
Additionally, two issues in regards to the Registry modification pointed to
here http://www.mvps.org/access/api/api0038.htm
1) The Registry key MUST be "No" NOT "no" or "NO"
2) On systems with XP or on systems with more than one user account,
you must add/modify the key in both HKEY_CURRENT_USER and
HKEY_LOCAL_MACHINE.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
"Tim Marshall" <TI****@PurplePandaChasers.Moertheriumwrote in message
news:ed**********@coranto.ucs.mun.ca...

Dave G @ K2 wrote:

>It clearly takes a little time to display the record, so does anyone
think this problem could be related to the speed that users scroll up
and down the recordset ? I've asked them to scroll slowly for a while
and see if it has any effect.

It is. I have this problem on A2K3 for images that are not embedded.
Scrolling too fast locks things up.

This is a solution offered by Steven Lebans on this group not too long
ago, here's the google link:

http://tinyurl.com/hmt7g

It's registry manipulation and therefore a bit scary to me and I was
instead thinking of trying to do something with the timer event, ie, save
the picture path to a variable, but not try to load until a couple of
seconds after and only if the picture path is the same at that time... to
avoid loading in response to every record scroll... I find when I do this
on one of my apps that uses a lot of pictures, the database locks up.

--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

[Tim Marshall]

Stephen Lebans wrote:

Tim that is an old post you are referring to. Here is a more current
version.

Thanks for catching that!
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "Whatcha doin?" - Ditto "TIM-MAY!!" - Me

[Dave G]

Thank you gentlemen. This feels like it might be a solution. I really
hope so, but won't be able to go on site to make the registry changes
until next week.

In the meantime, any idea why this problem has occurred just since I
upgraded from A97/W2000 to A2003/XP - is it just that the latter
combination is simply slower on the same hardware?

Dave