2. ASPRunnerPro General questions
  3. Multiple-step OLE DB operation generated errors
This topic is locked

Multiple-step OLE DB operation generated errors

 		11/5/2006 6:28:08 PM
ASPRunnerPro General questions
B
 bdegnan author

I created an ASPRunner application with MS Access using ASPRunner Pro 4.1 and got the error "Multiple-step OLE DB operation generated errors" when I tried to add or update a record. When I built the same application using the version 4, the error goes away. I also had an issue under 4.1, where I deleted a record and it did not go away. When I rebuilt the application using version 4, the record deleted successfully. For now, I am going to stay with version 4. It seems solid. I really like the new features in 4.1. However, it seems a bit unpredictable at this point.
B
 		bburden 11/5/2006

I am having the exact same problem as "bdegnan" but I don't have this problem with 4.0. I have even gon as far and re-creating the database which is a lot work because you have to do a complet do over with the text boxes and dropdown boxes etc.... I can't use the side by side columns in the visual editor, nothing is seeming to work for me. I guess I will have to stay with 4.0 for now, but would love to use the 4.1 because it does have features I really like. e.g. the time field is what is really important to me.
Thanks for the help
B
 		bdegnan author 11/6/2006

I did run into this error in Version 4. It seems that ASPRunner will generate input fields that exceed the size of the underlying database field. For instance, I had a state field that is defined as 2 characters in the underlying database. However, by default, I could enter more than 2 characters in the corresponding form input field and go an error. As soon as I entered just 2 characters, no error. I need to test this in 4.1 and see if that is the problem I am having there. I recommend that ASPRunner not generate input fields that are larger than the underlying database field.
What tipped me off to the field size issue was that I did manage to get a few records in and was able to copy and edit/save without problems. That indicated that there was some issue with one or more fields. Alot of times when I am testing, I will enter random characters into a text field, not paying in particular attention to the number of characters. I had entered something like "asdfasdefadf" into the state field, which caused the error described above.
Sergey Kornilov admin 11/7/2006

ASPRunnerPro 4.1 is able to read field size and automatically set maxlength property of text field to this field size. You still can change this property manually by double-clicking on this field on Add/Edit pages.