Query does not allow new records: OLEDB vs ODBC in Access 2K 
Author Message
 Query does not allow new records: OLEDB vs ODBC in Access 2K

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 the same SQL Server tables. The first query will allow new
records to be added, while the second one won't. Has anyone any ideas about
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

The second (OLEDB) query with only tblMeanCatApply *will* accept new
records, *until* I join it with tblMeanCat; then it won't. Yet adding
tblMeanCat to the second (ODBC) query *does* allow new records. Why?

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.



Sat, 12 Jan 2002 03:00:00 GMT  
 Query does not allow new records: OLEDB vs ODBC in Access 2K
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.


Quote:
> 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 the same SQL Server tables. The first query will allow
new
> records to be added, while the second one won't. Has anyone any ideas
about
> 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

> The second (OLEDB) query with only tblMeanCatApply *will* accept new
> records, *until* I join it with tblMeanCat; then it won't. Yet adding
> tblMeanCat to the second (ODBC) query *does* allow new records. Why?

> 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.



Wed, 16 Jan 2002 03:00:00 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. OLEDB Access 2000 project view does not allows new records, whereas ODBC query does

2. Works in Access Query, not through OLEDB or ODBC

3. Works in Access Query, not through OLEDB or ODBC

4. Works in Access Query, not through OLEDB or ODBC

5. New records not allowed by query...

6. New records not allowed by query...

7. New records not allowed by query...

8. Access will not allow new record in a subform

9. Access will not allow new record in a subform

10. Navigation Buttons - Not Allowing New Record Creation with Next Record


 
Powered by phpBB® Forum Software © phpBB Group