Multiple-Step error

[tomocb]

I'm getting "multiple-step ole db operation generated errors..." in a subform which is based on a stored procedure.

I have isolated the problem to the inclusion of field from a table that is a different table the one that is being updated in the select statement of the stored procedure.

If I only have fields selected from the table that I'm updating then it works ok.

Does anyone know why this is happening?

 

[tomocb]

btw. This is not the same as the write conflict error that is a confirmed bug by MS in a subform with an identity field in underlying table. This is resolved by using a refresh command with AfterInsert and AfterUpdate.

Instead this is only when I include fields from multiple tables in the select part of the SP.

This should be very quick for somone to recreate if someone could confirm that it is a common problem.

 

[tomocb]

Anyone?

Or are we saying that it is actually not possible to use a multi-table select statement stored procedure as the record source for a form in Access?!?!?

Surely that cannot be the case!

 

[tomocb]

Edit - If I can ask a slightly different question then; How are others using a subform datasheet stored procedure record source?

 

[tomocb]

Found the problem. It is because the foreign key that I'm updating in the
subform is part of a concatenated key in its foreign table. The reason it is
part of concat key is because I need to make it unique against the primary
key of the main form.

I wasn't previously setting the foreign key value programattically, but now
I'm doing so in the BeforeInsert event and it has fixed the problem, even
though Access automatically populates this value because it recognises as
part of the link child/master records.

It must be that it was populating it later than my new BeforeInsert sub
routine and consequently produced the error, which makes sense as this error
commonly relates to NULL values being parsed to tables when they should not.

Mods - Please close thread.