Jet requires 'uniqueness' to update and delete. An unique column/field
(auto-increment) and timestamp ensure uniqueness.
I hope this helps.
SW Florida's First ISP
----- Original Message -----
From: "Arthur Lyman" <alyman@stripped>
To: "Jon Slack" <Jon.Slack@stripped>
Sent: Monday, February 23, 2004 10:40 AM
Subject: Re: MySQL, ODBC, Access - why do I need to keep re-linking tables?
> Hi Jon,
> I found that adding an auto incrementing primary key solved the link
manager. I updated the Jet Engine and Microsoft DAC components first, and
that had no effect on this problem. Apparently ODBC needs a unique
identifier to ensure proper updating. I have not tested the multi-user
scenario but will shortly. I will let you know how that goes.
> Jon Slack <Jon.Slack@stripped> wrote:
> Hi Arthur
> I am the person who riginally put up the question you referred to in
yours. Like you, I had no replies.
> There are messages suggesting that one should use the latest Jet engine,
the latest ODBC drivers and (for some reason I cannot fathom) include a
dummy timestamp field in the MySQL table. When you update the table using
Access, the dummy timestamp field is (somehow) filled with todays date/time.
> Whilst this allowed me to close Access and then re-open it, retaining the
link, my application is designed to be executed from a network, by several
workstations. I have found that if a 2nd user opens my app (and links the
tables) then I have to relink the things the next time I use the db.
> I have yet to resolve this.
> Jon Slack
> Senior Technical Support Officer
> Division of Primary Care
> 1310 Tower Block
> University of Nottingham
> NG7 2RD
> Tel: +44 11584 66905
> Fax: +44 11584 66904
> There are 10 types of people in the world: Those who understand binary,
and those who don't...
> Arthur Lyman
> (914) 693-5113
> Do you Yahoo!?
> Yahoo! Mail SpamGuard - Read only the mail you want.