dancefloorlandmine: (Greenscreen)
dancefloorlandmine ([personal profile] dancefloorlandmine) wrote2004-09-21 12:09 pm

[SQL/Access] Evil Database of Doom

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?

[identity profile] d-floorlandmine.livejournal.com 2004-09-21 07:14 am (UTC)(link)
Queries: I have no idea - I've been trying to avoid getting too involved in it! [grin] Doesn't help that I don't really have any knowledge or experience of the Access/SQL combination concept anyway - and at present they haven't budgeted for training.

Personally, I much prefer VBA to macros. Unfortunately, it would appear that the "writing to" stuff is done using an update query, so it is copying data across, rather than performing it using the form's controls.

The [cough] so-called developer (who knew less than I do about Access when she started on this project) has now returned to the Antipodes, from where she's attempting to give remote support via email (ultimate arms-reach support).

[identity profile] thepaintedone.livejournal.com 2004-09-21 07:20 am (UTC)(link)
Unfortunately, it would appear that the "writing to" stuff is done using an update query, so it is copying data across, rather than performing it using the form's controls.

This is actualy the correct way to talk to the SQL server for edits. The alternative, binding the controls and/or form to the table via the linking would do horrible things to the server.

If they only could have done the same for reading :o/

[identity profile] d-floorlandmine.livejournal.com 2004-09-21 07:30 am (UTC)(link)
[grin]

[identity profile] incy.livejournal.com 2004-09-21 08:10 am (UTC)(link)
in which case you will need very long range weapons. Looks like development issues. Guessin git needs a bit of a rewrite. If it is any help I can try and see if I can get time to have a look (that is if you are allowed to show it to third parties) one night after work (mind you it might be into next week now).

[identity profile] d-floorlandmine.livejournal.com 2004-09-21 09:07 am (UTC)(link)
Thanks for the offer, but it's probably not strictly third-partiable - although I'll see what the Research Department (who own it) say ...