Presumably he doesn`t have admin privileges so when I sent the first build of the .exe the sysop had to arrange things to allow it to run.... All well and good everyone happy....
Unfortunately each time I issue an update to the app (just via a simple zip file to overwrite the older exe.. he has to call the sysop back again to reset things to run. )
The app is very simple 75% text files jpg's, a couple of dbf's and browser objects etc... nothing written to the registry etc etc....
Sysop is a helpful sort and has sent me this little questionnaire... not knowing much about the way these things work in this environment perhaps someone here could help me out...
I`m incremeting the build numbers each time... but other than that nothing significant is changing.. in fact the last update was to correct two spelling mistakes....The fact that the application runs under the administrator account and that Customer Person is able to execute the file afterwards would lead me to believe that the application it creating or editing a file or registry entry to register or configure itself. Typically I would use trace monitors to track down the problem but it can be quite a time-consuming process. Does the application need to register itself with any intermediary systems? (ODBC, .NET Framework, etc…)
Without knowing if, how or where the application is registering itself I cannot advise whether static build/version numbers will get around this problem. When Customer Person next calls with a problem I will see if I can narrow down the possibilities a little.
Cheers
Dave
Just about to press the button... here but had a thought... I`ve installed and uninstalled (though not employed) a couple of plugins in between builds/compiles.. could this be a possible cause???