I have a horrible suspicion that this question is either blindingly obvious or stupidly
impossible, but here goes.

I have been asked to design a database to store microbiological swab tests but this will
need to link to an existing employee table in an MS Access database. I would like to use
DBIsam, so does anyone know of a way to produce a SQL query based on tables in the
proposed DBIsam database joined to the MS Access Employee table? I should say that I
realise that I could use the Access table as a lookup table but really would prefer to
create a query that linked in columns from the Access table.

Many thanks,
Ian

Ian,

<< I have a horrible suspicion that this question is either blindingly
obvious or stupidly impossible, but here goes. >>

There are no stupid questions here, just an occasional stupid SQL answer
from me that Robert Kaplan promptly corrects.

<< I have been asked to design a database to store microbiological swab
tests but this will need to link to an existing employee table in an MS
Access database. I would like to use DBIsam, so does anyone know of a way to
produce a SQL query based on tables in the proposed DBIsam database joined
to the MS Access Employee table? I should say that I realise that I could
use the Access table as a lookup table but really would prefer to create a
query that linked in columns from the Access table. >>

You can't do the query in DBISAM and join the Access table, but you can do
it the other way in Access via our ODBC Driver.  The other option would be
to quickly pull in the Access table via the ADO components into an in-memory
DBISAM table and then use that in the query instead.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<You can't do the query in DBISAM and join the Access table, but you can do
it the other way in Access via our ODBC Driver.  The other option would be
to quickly pull in the Access table via the ADO components into an in-memory
DBISAM table and then use that in the query instead.>>

Thanks for clearing the fog on that one. I have just set up a routine today to dump the
Access table into a DBIsam disk based table, but the in-memory table sounds like a good
option to try out.

Many thanks,
Ian