Topic: Better (any) error messages on failed insert

Wed, 28 May 2008 23:50:32 GMT

Topic Description: We ran into a situation today where we were insert data using the data objects and it was failing with no error message text being returned. The .Insert() command returned False, but the .ErrorString was not populated. I think it should return more inforamtion as to why it failed and did not insert.

We had an issue previously with GUID column and default value not being set so I checked that but that was fine. I was then kind of stuck, and was looking at the intellisense help for the .Insert command and saw in there that a PK must be set on a table. I checked the .PrimaryKeyFields collection and found count of 0. So that meant we had forgot to set a PK on the table. we did that and regenerated the code for the objects and then it worked fine.

Any way that the error string can be populated with some kind of message on an .Insert call failing that a PK needs to be set. Can even be just general message of common causes of the .Insert call not succeeding.

Mike

Replies: 1
Last Reply: Wed, 28 May 2008 23:50:32 GMT
Reply By: Victor Gavriluk

Reply: Re: Better (any) error messages on failed insert

Wed, 28 May 2008 23:50:32 GMT

Hi Mike,

This is good suggestion and we add message in ErrorString when there is no primary key in table.

Also you can use ExceptionMode if you want catch any exception rather than Business Object catching for you if no PK no exception is fired.

Thanks,
Victor

Quick Objects Support

Akal Tech RSS Feed

Topic: Better (any) error messages on failed insert

Reply: Re: Better (any) error messages on failed insert