I have an SQlitening problem that I need help with. I have a SQLitening/SQLite database program that runs great in LOCAL mode. But when I try to Connect to the database via client/server REMOTE mode. Then I get error messages on the slSEL statements. See the screen print attached.
The program will connect to the remote database and the slExe slBuildInsertOrUpdate works. I know I am connecting to the database. But the slSel give a wierd error message.
I created a small FF3 project that demonstrates the problem. If you run this program in local mode no error message. But if you set up a Client/Server Remote mode then the problem willoccur.
Could someone here take a look and see if they can find an explanation why REMOTE mode won't work .
Took me a while to sort out the problem though it was quite obvious, because I had experienced the same before.
On you client you are using SQLitening version 1.20 files. If your server runs version 1.30 this will exactly happen. (Error near CT). Use version 1.30 files on the client and the problem will disappear.
I attached the project with SQLitening 1.30 dlls.
Rolf, thank you for taking a look.
Version confict.... I went through my directories and made sure that they all have version 1.30 (the one you included in the zip). Thanks for catching my error.
Good news the little test program now runs with out a error.
Bad news is the larger program gets an SQLitening error of -14 invalid set. But the strange thing is that the program runs fine in LOCAL mode.
Here's the screen print of the error message.
Any I deas about this message? Or, more to the point how I can correct this?
You are probably using the same set number for an slSel as you used for an still open set. If you did not declare a set number then it defaults to 0. You must either use slCloseSet or use a different set number.
Rolf,
Thanks for the tip. That worked! The program now is successfully working in Remote Mode with the database on the Server.
I found that I needed to place an slCloseSet right after the slConnect and slOpen statements. I would not have guessed that it would be need there but when I placed the slCloseSet there the problem went away.
That is a big relief for me. I knew there must be something simple that I was missing but I just could see it.
I will use slCloseSet like pixie dust and sprinkle that statement at the top or end or every function! ;)
Thanks again very, very much.