On 2014/02/22 01:37, Geo Wil wrote:
As for the fail path issue, it is not an issue or at least it has never been for me. The way I understand it is that if you just put the file name into a function requesting a path in Windows it will look in the folder the process is running from for that file. //
Yes of course, but the problem is the typical folder a program will be installed to (which may not be the case in the dev machine) is c:\Program Files\ and that path is special and protected, and there is no sub-folder of that path that windows will allow you to keep a file and make changes to it unless your manifest specifically requires it (and even then the user will be bothered every time for access grants). You need to save the data very far away from the exe, such as the program-data folder I described earlier. You may have switched off the UAC on the dev PC, but it will be alive and well on an intended user's PC and it will not allow you (or anyone else - which is the beauty of it) to overwrite any file inside your program's exe folder or sub-folder thereof.
Although you are right, I should be a bit more explicit with the path, maybe use ./Databases/[filename] so that it will explicitly look in the same folder and not have to use a default behavior that can sometimes be fallible.
Being explicit about the name is of no consequence when the resulting location of the file is still inside a protected folder. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
