[personal profile] tamaranth
Has anyone else experienced data corruption in Memo fields in Access (pref Access 97) databases? If so, any hints or tips for making it stop? (Yes, I have already considered making it non-Memo, but this would inconvenience the poor li'l users.)

I have had my suspicions about this problem but it's not something I've encountered before: mind you, QualityTatPurveyor has a very peculiar setup.

Date: Wednesday, October 13th, 2004 04:26 am (UTC)
From: [identity profile] spride.livejournal.com
What sort of corruption?

Where I work, one department has implemented a *data warehouse*, if you please, in Access 97. I don't normally miss an opportunity to tell them they're not only skating on thin ice but dragging braziers onto it and jumping up and down on it. Which is a roundabout way of saying that I found most Access 97 development issues went away when things were migrated to a more modern version. Assume that's a no-go where you are?

Date: Wednesday, October 13th, 2004 04:54 am (UTC)
From: [identity profile] tamaranth.livejournal.com
Corruption of the '#Error' type -- e.g. contents of field disappear, errors when paging past record, indexing errors.

It's not an ideal situation: eventually it will be migrated to Access2000, but this is not something I have any control over: neither is my (repeatedly recommended) preference for SQL Server database and Access front end.

Date: Wednesday, October 13th, 2004 05:05 am (UTC)
From: [identity profile] spride.livejournal.com
Not seen that, thankfully.

http://www.experts-exchange.com/Databases/MS_Access/Q_20161754.html has some views, random or otherwise. The one from mgrattan is worth checking...

January 2026

S M T W T F S
     1 2 3
4 5 6 7 8 910
11 12 13 14 15 1617
18 19 20 21222324
25 262728293031

Most Popular Tags

Expand Cut Tags

No cut tags