Here's the pertinent info

Platform: Win
Python Version: 2.6.5 on win32
Dabo Version: Version 0.9.3; Revision ~6238
UI Version: 2.8.11.0 on wxMSW

It had been a while since I had done an SVN update. I was at revision 6129
and did an update to the current 6238. Now I get the following error when I
open my add record form to ...well...add a record:

ERROR - Failed to set RowNumber. Error: (1064, "You have an error in your
SQL syntax; check the manual that corresponds to your MySQL
server version for the right syntax to use near '%s  \n limit 1' at line
12")

After I dismiss this prompt, add my info to the form, and hit save the
record gets saved/added to the database.

I did some reverting and was fine to revision 6232. Updated to 6233 and the
error  above started.
The revision logs says:

Refactored CursorRecord out of dabo.db.dCursorMixin into dabo.db. Now
both dCursorMixin and dBizobj can use the class to instantiate their
own Record instances. This effectively means that assigning to
biz.Record.field no longer calls cur.setFieldVal() directly but
instead calls biz.setFieldVal(), allowing easy interference to be
run by appdev code.

Added biz.afterSetFieldVal() hook method.

Refactored biz.setFieldVal() to do away with the ret value, as dCursor
doesn't return anything but None anyway.

so I know I'm on the right track but lack the knowledge to determine
anything beyond what I have traced here with the exception that this error
only occurs on the couple forms I have that contain dDropdownLists. The one
form I have without it does not throw the error. My drop downs are similar
to those it the pycon Hours tutorial.

My entire app is a CD app.

HELP!

Carey


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: 
http://leafe.com/archives/byMID/[email protected]

Reply via email to