I could really use some help on this one.

The following two queries seem identical to me with the exception that the
first uses linked ODBC SQL Server tables and the other is an OLEDB Access
project linked to SQL Server tables. The first will allow new records to be
added, while the second one won't. Has anyone any ideas on what I can do to
get the OLEDB query to accept new records?

Thanks,
Gary

SELECT dbo_tblMeanCatApply.MCApplyID, dbo_tblMeanCatApply.MeaningID,
dbo_tblMeanCatApply.MeanCatID, dbo_tblMeanCat.Category
FROM dbo_tblMeanCatApply
INNER JOIN dbo_tblMeanCat
ON dbo_tblMeanCatApply.MeanCatID = dbo_tblMeanCat.CatigoryID;

SELECT tblMeanCatApply.MCApplyID, tblMeanCatApply.MeaningID,
tblMeanCatApply.MeanCatID, tblMeanCat.Category
FROM tblMeanCatApply
INNER JOIN tblMeanCat
ON tblMeanCatApply.MeanCatID = tblMeanCat.CatigoryID

A query with tblMeanCatApply will accept new records until I join it with
tblMeanCat. Then it won't. Yet adding the second table with the ODBC query
does allow new records.

Both are Access 2000 files linked to the same SQL Server tables. I'd like to
use the OLEDB Access project for the greater efficiency over ODBC and
because ODBC introduces the update bug when adding new records.

Solution:
Turns out I don't need to have a query that allows new records; simply
setting the Unique Table property of the form or subform allows the Access
project cached recordset to be updated and the form or subform to take new
records.

I read about this in "About updating data in a Microsoft Access project or
data access page" in online help.