v_pozidis wrote:

A stupid question. What do you mean WAL???

I can answer your first question easily.  WAL stands for Write Ahead Logging, which allows SQLite to have multiusers access it.

However, these are special cache files that it writes, and won't automatically commit users data changes to the database. It basically will wait until the last user has closed their connection with the DB (with MVD that is just closing the application) and then it updates the database. I believe it commits data to the database as the cache reaches a certain point.

As for your other question, I'll have to think about it and maybe someone else can answer off the top of their head.

Thank's for your quick response. So this is not a real time connection to the database. it is not useful for my case. I t will be great if someone could answer the second question.

A stupid question. What do you mean WAL???

I can answer your first question easily.  WAL stands for Write Ahead Logging, which allows SQLite to have multiusers access it.

However, these are special cache files that it writes, and won't automatically commit users data changes to the database. It basically will wait until the last user has closed their connection with the DB (with MVD that is just closing the application) and then it updates the database. I believe it commits data to the database as the cache reaches a certain point.

As for your other question, I'll have to think about it and maybe someone else can answer off the top of their head.

vanadu55,

You need to copy the following files to a folder on each client workstation in addition to your EXE file (Don't put them on the desktop).

1. Script folder containing just the dcu file.
2. Forms.xml .
3  sqlite3.dll .
4. Settings.ini
5. Any graphics.dll  if it exists +  image files if they exist.

Now you can either manually change the server path  to the database in the settings.ini file or install on one PC, run the program and then follow the dialogue prompts when your program can't find the database.  Once you have one settings.ini file set up, you can just copy that one to each PC.

Once that is done then you can place a shortcut on the desktops if you so wish.

Thanks for the explanation!

You need to copy the following files to a folder on each client workstation in addition to your EXE file (Don't put them on the desktop).

1. Script folder containing just the dcu file.
2. Forms.xml .
3  sqlite3.dll .
4. Settings.ini
5. Any graphics.dll  if it exists +  image files if they exist.

Now you can either manually change the server path  to the database in the settings.ini file or install on one PC, run the program and then follow the dialogue prompts when your program can't find the database.  Once you have one settings.ini file set up, you can just copy that one to each PC.

Once that is done then you can place a shortcut on the desktops if you so wish.

m.alin,,
Try placing the app on the client workstations, but keep the database on the server.

Can you tell us more how to do that? If i move the app to the client workstations how do they link to the database on the server?

Thanks in advance.

Thanks.

Alin

Just a warning, if you intend to have the SQlite database file on a network share drive and an IT department runs a cache clearing program in the background, you will lose data and get locked database messages.

If there is no cache clearing program is running, then there shouldn't be any problems.

To enable WAL mode in sqlite, open your database in a database browser such as DB Browser for SQL Lite and type in under the SQL tab

PRAGMA journal_mode = WAL

Close the browser and when you next open your program you will see 3 extra files appear, these are the caching files.

If this doesn't work for you, then to disable Write Ahead Logging open the DB browser and type into the SQL tab

PRAGMA journal_mode=DELETE

Are you using SQLite or MySQL?

I'm using SQLite.

I've placed the application on the server and we want to work 3-4 users in the app.
As soon as the second user is connected to the application, the app is getting very slow, the data and the forms are loading very slowly.
What shall I do to make it work? In this moment the database has approx. 250 Mb and is growing.

I want to mention that, production needs only to book some data in their special form, planning to put orders in the app and print the papers in his special form.
Thank you for a solution.

Br,
Alin