Well, you don't have to install VFP on the target machine.
If you are running with a .exe file - you can mostly just copy that. Exceptions would occur if you added features that encompassed additional controls, fonts etc.
That aside, the answer generally is to make the target machine check a source to see if the version being run is older than the source and if so download the source file first.
Plan B is to ALWAYS down load the source first - regardless.
I have used a local view in one of the forms, when the form is run on the target machine it is looking down the test data path not the application data path.
I could create the view programatically in the load event
I am glad that you found the problem. I have a hard time following your thread - no offense meant. It seems that at the beginning you were talking about some kind of Autoupdate feature and in your middle post you are talking about what appears to be a default path or search path issue and then here at the end you say that the solution was to remove buffering from your view. You might try using different threads for different problems or maybe these are all related somehow and I am just too dumb to see it.
Because I had used the dataenviroment in the form this had the effect of storing the path to my test data. If the EXE is "Installed" it will change it.
The solution is to create SQL views "on the fly". At this point I realised I had been going round in circles because I didn't need views anyway. Why not buffer the tables?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.