At 09:40 AM 17-01-02 -0800, you wrote:

>I thought that by assigning SQL to the InsertSQL property, IBO would do the
>rest(do the update when posting on the joined table), hence the request to
>keep all column names properly named and "unique" and use them throughout.

Yes, it's a good rule because logically those params "belong" to the main dataset.

Sorry, I failed to notice that you were talking about your InsertSQL property and not passing the params to a DSQL component...

Yes, I believe params of the same name should pass directly to the InsertSQL. There isn't any other mechanism to get them there!

Trace what is happening in the SQL Monitor and try to find out exactly what's going on. Especially, look to see whether the Insert method is preparing the InsertSQL statement (you should see the input params listed in the monitor, with <NULL> beside them. At execution time, you should see the same list but this time containing the values from the dataset's current row.

I'm puzzled as to why you have MasterParamLinks defined for the dataset. I didn't realise that your joined dataset was detail to a master-detail relationship...sigh...I should imagine the Params[] in this structure are a right royal mess. It's really hard to troubleshoot a problem when you only supply part of the information.


regards,
Helen Borrie (TeamIBO Support)

** Please don't email your support questions privately **
Ask on the list and everyone benefits
Don't forget the IB Objects online FAQ - link from any page at www.ibobjects.com