Thank you both. It is a console app that I'm using to test some basic SQL routines.

Karl: That box is checked.

Wolfgang: I'll try to write an error handler based on the example you provided.

The adventure continues!

When I run a test application in XIDE it shows a black error screen that quickly disappears.
How can I capture that error?
Is it saved somewhere? Is there a setting I've missed?

Thank you once again, everyone. This code compiles and works: LOCAL cDB AS STRING LOCAL oConnection AS SQLConnection LOCAL oStatement AS SQLStatement LOCAL cStatement AS STRING * trying to open an SQLite3 database * here is the ODBC driver: * http://www.ch-werner.de/sqliteodbc/ // open everything ...

Thank you, Wolfgang, but I got the same result.
Here's a zip file with the project and the db in case anyone wishes to try.

Trying to set up a basic SQL test app. Using SQLite3 ODBC. Here is the code and the compile errors. Thanks in advance for any help. VO Dialect has been selected. FUNCTION Start( ) AS VOID LOCAL cDB AS STRING LOCAL oConnection AS SQLConnection LOCAL oStatement AS SQLStatement LOCAL cStatement AS ...

Wolfgang, Yesterday Chris Pyrgas talked me into leaving VO and I decided to take his advice. So if you grow weary of logging onto this forum every morning only to see another dumb question from me, blame it on our friend Chris. :) I tested the following libraries in a VO-exported application: XSharp ...

I wrote this many years ago. Never fully implemented because I couldn't get everything to work in VO.

https://joecurran.net/advice/dbf_to_sqlite.htm

My strategy was to move the DBFs to a text/csv format and then import into the SQL flavor of your choice.

Another possibility would the to use the XSQL classes. They are the VO SQL Classes, but instead of using ODBC, they are using ADO.NET as underlying database layer. XSQL classes? That's new to me. Do you mean the SQL classes in XSharp ? If you look up SQLConnection{} in the help file it says ODBC ...

Wolfgang, I concur with your findings on terminal server (currently known as RDP or Remote Desktop). Under that setup all the processing is done on the server -- no network pipe except for the screen rendering. Which probably explains the performance advantage. One client has at least 50 login ...

Ba-da-BING!

That worked.

Thank you, Robert