> Making any progress on this? I've got a (really) simple app. that dies when I try to disconnect from SQL Anywhere. I was originally using remote views but I was having problems with my app and the SQL Anywhere ODBC driver locking up when I tried closing the connection (like you're doing above).
>
> So, I just switched to SQL Passthrough. I can open a connection, pull down the information w/o any problems at all. As soon as I try issuing the SQLDISCONNECT the application hangs. More specifically, it works the first time but hangs if I attempt to reestablish / disconnect again.
>
> I've tried searching Sybase's web site for any info, updated drivers, etc. with no luck.
>
> I'm really beginning to wonder about VFP's ODBC implementation. For a language that's supposed to be specifically geared to data access, I haven't been having much luck. This is the second time I've tried using an ODBC connection in VFP to access another system's data, and this is the second time I've run into major problems w/something that should be really easy. The first ODBC driver (not SQL Anywhere) completely killed VFP - it would bomb out immediately. I had to switch to Access. And now this. I think I'll try Access again - or maybe Visual Basic.
>
>Sigh...(sorry, just venting)

Sadly, Paul, no. We've tried everything, or so I think. Another consultant is talking her through copying the oleaut32.dll file from one of the computers (that works) to the one that doesn't. Don't think that will work, but we'll see.

The client realized that the Windows 98 workstations were working, and the Windows 95 stations were experiencing the lock-ups. She got a new computer (with 98) and hooked it up to the network with no success. She got the same lock-ups.

Could this have anything to do with the network card? Or the network drivers? Why would it work on some and not on others?

JR