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.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
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.