Haven't been called "Simon" often in my life, I guess there's a first for
everything! :)
Strange. I get it all the time.
Well, now I know how it feels too!
There are two problems, and they come up repeatedly on this and other lists: (1) the 'default' folder for a Windows app changes
depending on whether it’s your own code or a DLL opening a file for you. So if you start using a precompiled DLL suddenly your app
starts behaving differently for no apparent reason. (2) Windows doing the UAC thing you explained so well in your previous post.
Yes I have dealt with this a lot, I'm mostly a Windows developer of some stuff that needs to be very user friendly,
zero-interference install & operation etc, so paid my schooling fees in UAC town a few times over. The truth is the UAC is such a
blessing in security terms, but such an inconvenience to most windows users who have not been brought up (if you'll allow me the
term) with root securities such as is second-nature to a Unix, Linux or most derivative systems and their users. "I Can't do the new
thing" syndrome.
That said, even to seasoned devs it can produce some very surprising effects if you are not completely up-to-speed. Hence me
attempting a layman explanation earlier, but to really know it in depth will of course take some weeks worth of explanations, can't
hack it in two paragraphs. I can promise you one thing though, it is in no way random and even though you say "for no apparent
reason", there is no mystery about it, the reasons are clear and well documented (if a little laborious to read).
It's much like a traffic system of a town. You have places you can drive, and places where you can't, and places where you can
drive, but shouldnt, etc. Road signs are provided but meaningless if you don't know what they indicate. Lol, I'll stop right here
and refrain from labouring a long-winded explanation on the forum readers, but if anyone is having some trouble with it still,
please feel free to drop me an email.
The only solution I ever found (for a far earlier version of Windows) was to require a full path to be specified by the user,
either asking for it to be typed in, or using the System call which presents the folder GUI and using the path it returns.
Easiest is to just put it where it is safe (read: where windows trusts it). A simple API call to the Shell with any of a dozen
documented standard path reference IDs will return specific path strings to such locations (depending on the need) and will be
transparent to the user, your program, the linked libraries, and more importantly, not be affected by the UAC.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
