There are a huge number of matches when googling for the access #Deleted problem.

I have the unenviable task of converting the database backend of a load of
established MS-Access databases, currently using .MDB files over a slow,
not-100%-reliable, network link, to use some for of SQL backend, initially using
MySQL.

Not knowing much about SQL, and inheriting a pile of visual basic stuff in
access which I also know nothing about (I hack C and Fortran), I can just about
get my head around creating databases, tables, and users, and connecting said
tables with MyODBC.[1]

And I ran headlong straight into the #Deleted problem, which in the context of
the existing access setup is a showstopper.

Is there a definitive guide as to what versions of MySQL/MyODBC, and what subset
of column types and properties will not generate this problem? I keep seeing 'I
did XXXX and it went away', but when I try something similar (say, adding a
timestamp column) the problem is still there.

Jim
--

[1] Further complicated by the fact that my development PC does not have MS
Access installed, and I end up having to use VNC to a machine on the other end
of said not-100%-reliable network link to talk to one that does, because we
won't shell out for a license for my machine. Yet another 'You are required to
do this with no resources, no budget, and no knowledge about the subject in
question. PS. We want it finished by last year'. Where did I leave my cluestick?