Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error 2074 "This operation is not supported within transactions"

Status
Not open for further replies.

LittleSmudge

Programmer
Mar 18, 2002
2,848
GB
But I'm not using Transactions !

I have a fairly simple Front end database connected a MySQL back end.

Connection via ODBC
Some ADO recordsets for populating forms and writing data
and PassThrough queries for other things like populating combo box rowsources etc.

This has been working fine. It has just started playing up and I can't find out what has changed.

It occurs following a combo box AfterUpdate event.
The code in this event causes the SQL string in a PassThrough query to be edited with the data from the combo box.

This Pass through query is the RowSource of another combo.
( Thus I control the contents of the second combo based on the value selected in the first. )

Any idea what the problem is and why it has only recently started ?




G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.
 
Is the form bound to an odbc-linked sql table? Could the form have the table open for edit, thus starting a transaction on the backend db?
--Jim
 
No Jim

The Form is unbound.

It does comtain a subForm. That subform in continuous view is bound to another PassThrough query.

The subform's PT query does include the tblProject as one of it's tables - but being a PT SELECT query it is Read Only anyway.


The First Combo box selects a Department.
The AfterUpdate event then edits the PT query that is
SELECT * FROM tblProject WHERE DeptRef = value from cboDept

I can't see that this simple query should be locked in any way.





G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.
 
Found out what's causing the problem

It is a Windoz Hotfix update.

I finally realised that the only machines being affected were Windows 2000 Pro operating system machines.

The Update Rollup 1 for SP4 is causing the problem.

MS themselves have issues a version 2 of this hotfix because the first one caused soo many problems.
The second version does not fix my problems though. So I've had to completely uninstall the Pollup 1 for SP4 package any my applications all work fine again.


'ope-this-'elps anyone else in a similar position.



G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top