Mathew,
Typically this happens when you have a view with uncommitted, buffered changes attempting to post its changes (probably when you browsed it) via a connection that has already been closed.
To verify, use the debugger the next time you get this problem and look for a view with uncommitted changes. If you TableRevert it, you should be able to continue.
I would suggest checking your code for anything that would call SQLDisconnect on your connection.
Not sure how many connections you need. I've heard testimonials on both sides. We share connections when using non-updateable, lookup views and separate connections for updateable views.
Hope that helps,
---J
>Hi All,
>
>I have successfully connected to the SQL server and the handle value returned was 1. I used this handle value throughout my project. I set most of the tables updatable using (SQL pass through). In one form I have successfully updated the table and within the same form I called the second form. In the second form, I saved the data and I got not error message. After, I closed all the forms and try to browse my VFP cursor I got this message "Connection handle is invalid". When I viewed the data using the SQL enterprised manager the first table was updated, but the second data was empty. I thought you only need one connection handle throughout the project.
>
>Does anyone knows why "Connection handle is invalid"? Any help or suggestion is appreciated. Thanks