At 10:55 AM 10/25/99 +0200, Milan Salajka wrote:
> > Hmm... actually, that brings up one possible point -- I did get a bizarre
> > message when in Microsoft Access, trying to change a field in a linked
> > mysql table, that someone had already changed the data. This wasn't true,
> > but I was consistently unable to make changes. Maybe this is related?
>You should have a TIMESTAMP type column in table, it will solve THIS
Well, we do have a TIMESTAMP column -- and it is still happening.
It seems to be only affecting 'char' fields -- I can change integer fields
without this error.
>(Anyway there are some other "problems" when you are using MyODBC &
How might those relate to our continuing problems with IIS on an NT? IIS ->
myODBC --> mySQL (over the LAN) doesn't go via access...