>>The same thing happens when I use the View Designer. When I use SQL
>>Passthrough
>>functions I get no error messages.
>
>Tom is right, I smell a bad driver....
>
>>I get the error right after exiting the browse window and trying to
>>close the databases or the view itself.
>>I tried the same program on a Win 95 machine and it worked just fine
>>*but*
>>I can't upgrade my machine to Win 95 yet. I tried an ODBC inspector
>>program
>>and it shows that the error is issued when the ODBC driver tries a
>>SQLDISCONNECT at the close statement. What transaction could still be
>>pending to be executed ?
>
>How many records is the select statement returning? If it is a bunch, perhaps it is not done downloading them yet. 16-bit systems act kinda funny sometimes....
>
>>My machine is a DX4/100 16 Mb running Win 3.1 on a Netware 4.1 network.
>>32-bit x 16-bit drivers problems ?? How can I be sure I'm
>>using the correct drivers ? I assumes VFP installed them
>>correctly..
>
>I wouldn't make that assumption. Remeber, 3.0 was shipped before the ODBC drivers were even in beta, so.... Normally, I would suggest to make sure you have the latest drivers from the MS site, but people are telling me that when they download them and try to install them, they get an "this has expired" message. If you have the latest version of VB (4.0, I think) I know they have working 16 and 32 bit drivers.
>

i downloaded these drivers last week and they're working fine for me...


>
>HTH,
>Scot.