|
|
Posted by teddysnips on 09/11/07 19:30
On Sep 11, 5:31 pm, lgeastw...@gmail.com wrote:
[...]
> Just a few things I might look at. Maybe you have already.
> Have you compiled the code module?
Both compiled it, and also decompiled and recompiled. Interestingly
(or not, YMMV), this crashed Access every time I tried to load the
application.
> Have you checked for field name errors on the form?
Yes.
> Is your form based on a query that is not updateable?
No, it's based on a linked table.
> Have you refreshed the link to the table?
Many, many times. I've also deleted and recreated the DSN used to
connect.
> Have you tried creating a new table and appending records from the
> problem table?
Better than that, I've entirely recreated the database from scratch -
i.e. scripted it, then created an import using DTS. Took a while mind
you. Didn't do any good.
One thing that I didn't mention, mainly because it's not something
that has changed recently (in fact it changed about two years ago, and
I didn't notice until today when I was sitting with the client), is
that the application was developed under Access 2k (makes sign of
cross) but is actually running under Access 2k3. So my latest wheeze
was to create a new Access 2k3 database, import all the objects from
the 2k database, recompile, save in 2k3 format. Haven't had a chance
to try it out yet - my client left the office to play golf at midday,
since the lack of the application meant he couldn't do any work.
Thanks, anyway, for all the suggestions. I'll let you all know the
outcome of tomorrow's little experiment. If it doesn't work, I think
I'm probably going to suggest that I rewrite this as a .NET
application. Shouldn't take too long, since all the forms ane
designed, the database exists, and the VBA would make a perfectly
acceptable pseudo-code design.
Edward
Navigation:
[Reply to this message]
|