> regards
> Steve
> --
> Steve Holden +44 150 684 7255 +1 800 494 3119
> Holden Web LLC/Ltd http://www.holdenweb.com
> Skype: holdenweb http://del.icio.us/steve.holden
> Recent Ramblings http://holdenweb.blogspot.com
>
> --
> http://ma
Greg Corradini wrote:
[actually, her wrote it here but I moved it to the bottom]
> Steve Holden wrote:
>> Greg Corradini wrote:
>>> Hello All,
>>> A few weeks ago, I wrote two scripts using mx.ODBC on an Access DB. Among
>>> other things, both scripts create new tables, perform a query and then
>>>
of Access when it sees words it
> can't parse.
>
> regards
> Steve
> --
> Steve Holden +44 150 684 7255 +1 800 494 3119
> Holden Web LLC/Ltd http://www.holdenweb.com
> Skype: holdenweb http://del.icio.us/steve.holden
> Recent Ramblings http://h
t;> Driver] Too few parameters. Expected 4.', 4612)
>>
>> The real stinker, however, is that after it bails I can manually call
>> mycursor.execute('An SQL Statement'), then call my insert statement in
>> the
>> Python Shell and it works fine.
>>
>&
Greg Corradini wrote:
> Hello All,
> A few weeks ago, I wrote two scripts using mx.ODBC on an Access DB. Among
> other things, both scripts create new tables, perform a query and then
> populate the tables with data in a dictionary that I've uploaded from
> elsewhere. These scripts have run hundred
igure out how to reconcile this problem. Has anybody run into
> this before?
>
> Thanks
> Greg Corradini
> --
> View this message in
> context:http://www.nabble.com/Help-Understanding-mx.ODBC-Error-tf3602497.html...
> Sent from the Python - python-list mailing list archive at Nabble.co
cute('An SQL Statement'), then call my insert statement in the
Python Shell and it works fine.
I just can't figure out how to reconcile this problem. Has anybody run into
this before?
Thanks
Greg Corradini
--
View this message in context:
http://www.nabble.com/Help-Understanding
