First thing to try would be to remove those parts of the Connection String to see if you go back to getting your original error, or if you get the new error.
If you get the original error after removing those parts, then it might be that SambaPOS does not support those parameters in your connection string.
If you still get the new error after removing those parts, then there is a problem finding the DB in that path.
What was your original Connection String before you tried changing it? Did it always include the Path? Or just the Filename?
It always contained the full path since the beginning, as we wanted to take a full backup of the database folder manually using windows task scheduler. Prior to the changes following was the settings file:
Once the following of the connection string are removed the program opens fine.
Max Database Size=256;Persist Security Info=False;
However once POS is clicked it shows the same exact previous error which says that the database is larger than max configured. Also I found out that on the connection string if I just key in the database file name it creates a total new database on the application path located under Program files. And once again when I key in the Max Database Size into the connection string application returns with an error that it cannot connect to the database.
Hi kendash,
Thank you a lot for the feedback, I guess that should be better.
Can I please have a guide to migrate the existing database to SQL and upgrade of the software to the mentioned version. And I really need it urgent as the service has been down for more than an 48hrs now.
Thanks QMckay. That worked, i just changed value from 256 to 500 and output ran.
Now the problem i encounter is it exported more then 25 files instead of one per instruction on migrating. Which one should i use to copy and paste query.
Ive only done this once and ended up with maybe 5-6 files, I imported them one by one if I remember right.
Probably dependent on how long you ran in CE and how much sales history you have.