Steve Holden wrote:
>
> 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
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
>>>
Steve,
As always, thanks for your consistent help on matters big and small.
I've managed to solve the problem, although I'm scared b/c the bug is still
elusive.
I dumped and deleted my seperate Access DBs, created new ones and tried
running the scripts on old data (that these scripts were able to
Thanks for you help kyosohma,
Unfortunately, the data I'm using isn't chaning either. I've reused data
that these scripts have successfully used before, but that won't work with
them now.
kyosohma wrote:
>
> On Apr 18, 1:36 pm, Greg Corradini <[EMAIL PROTECTED]> wrote:
>> Hello All,
>> A few w
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
On Apr 18, 1:36 pm, Greg Corradini <[EMAIL PROTECTED]> 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
> e
