Switching to mySQL

[David]

Hello

I have a query locally written in my Access DB that I have used quite
successfully for a while now. It starts like this

SELECT Pax.CNNo, Pax.FirstName, Pax.LastName, Pax.FlightNo, Pax.Destination,
CheckIn.Camp, CheckIn.Agent, CheckIn.Time, CheckIn.Boarded, CheckIn.NoShow,
CheckIn.MissedBus, CheckIn.DeniedBoarding, CheckIn.Shuttle, Pax.PaxNo,
Pax.LocatorCode, Pax.CompanyContact, Pax.PaxChangeFlight
FROM Pax LEFT JOIN CheckIn ON Pax.PaxNo=CheckIn.PaxNo
WHERE (((Pax.FlightDate)>=Date()));

In the form where I am using the information the field in the checkin table
are shown as null until I click on one of the check boxes (CheckIn.Boarded)
then Access creates a record in the CheckIn table with CheckIn.PaxNo =
Pax.PaxNo

I just recently migrated my base tables (not my queries) to a mySQL database
and this is no longer responding the same. It will no long let me click a
null checkbox.

How do I fix this?

David

 

[Michel Walsh]

Not all databases allow you to update the unpreserved side of a join, and
even less to append a new record ( update existing / append new ) such as
Jet does. As example, MS SQL Server does not do it, and it just seems your
MySQL version does not either. That are the kinds of problems we got when we
change of platform, sorry.


Vanderghast, Access MVP

 

[David]

Thank You Michel

I thought that might be the case.
My work around is to append a blank matching record in the MouseDown event
of the check box which does about the same thing before the Click event of
the checkbox fires.