M
@Jonathan Holland said: Access as a backend is pretty pointless when you can use SQLExpress. You're confusing 'Access' with the database engine. Access is purely a graphical database front-end and horribly bad application development environment (in terms of userfriendliness of the GUI). Access natively used Jet as its backend engine, and could talk to any other engine you wanted, as long as there was an ODBC driver for it. Unless you specified otherwise, you'd doubleclick the .mdb and be talking to Jet in the background without configuring anything. @Jonathan Holland said:Access has a horrible locking method, and you risk having stale data with concurrent users, because it batches updates and inserts.For all the marketroid blather about multi-user support, it was essentially grafted onto Jet as a hack. Anyone doing anything serious in the way of development would opt to use a better engine than Jet. But for single-user purposes, Jet was quite nice.@Jonathan Holland said:you don't have to go change the True/False fields to bitsYou'd think ODBC would be smart enough to do that for you. After all, it was supposed to present a unified and consistent interface to all and any database types. But Openly Dead-Brain Crap was badly designed from the get-go, as with any early Microsoft protocols. Just enough to work in most situations, and screw anyone else who needed something more, until the v3.0 revision came out (remember, M$ never gets anything right until v3).