[SQL/Access] Evil Database of Doom

[dancefloorlandmine]

There appears to be a slight glitch, in that an unnecessarily complicated process is not working correctly.

Background information
The database is running on SQL Server, with a Microsloth Abscess 2000 front end on each relevant desktop, using linked tables.

Problem
The developer created a drop-down to enable the selection of previous contacts. This then triggered a macro (mutter mutter) which ran a Refresh operation, and a pair of queries (no, I don’t know why a pair either), which populated the main table with data from the saved information on the previous contact. However, this does not then display on the form on screen. Just to add to the fun, most users will view the form with the "Data Entry" property set to True.

When, on the test database, the tables were imported instead of linked, and a “repaint” operation solved the problem. However, when using the linked tables on the real thing, nowt - the repaint doesn't seem to work.

Anyone got any ideas?

Comments

[thepaintedone.livejournal.com]

Not without actualy seeing the thing in the flesh. To be honest it sounds like one of Access's weird little quirks (of which it has many) rather than anything specific you're doing wrong. What you are doing is so bastard bad and wrong, on so many levels, that trying to troubleshoot it is a bit like worrying over a papercut on a dismembered corpse.

If you can zip up a copy of your client and mail it to me I can try to decontruct what it's doing, but without the tables as well it'll be half guesswork.

Incidentaly, please don't refer to that person and as a developer. Anyone who would voluntarily create such a Frankenstein mess needs killing.

Also, I'm half way through migrating our SQL solution to Access, if you want some more pointers on how to do things properly, let me know.

[thepaintedone.livejournal.com]

That should of course have read Access solution to SQL.

[d-floorlandmine.livejournal.com]

[grin]