Welcome To The Home Of The Visual FoxPro Experts  
home. signup. forum. archives. search. google. articles. downloads. faq. members. weblogs. file info. rss.
 From: Stefan Wuebbe
  Where is Stefan Wuebbe?
 Stefan Wuebbe
 To: Khurram Tahir
  Where is Khurram Tahir?
 Khurram Tahir
Subject: RE: Slow Work
Thread ID: 393899 Message ID: 393964 # Views: 37 # Ratings: 0
Version: Visual FoxPro 9 Category: VFP and .NET
Date: Friday, December 27, 2013 9:37:17 AM         

> >
> > If you mean this one http://archive.msdn.microsoft.com/FoxPro/Release/ProjectReleases.aspx?ReleaseId=125 ,
> > you already got the VFP9 SP2+Hotfixes runtime files installed
> > ...
> >
> >
> >
> > ... so you would not want to copy another set of runtime files again somewhere manually.
> >
> > "VFP.EXE" probably is a "YourProject".EXE rather than the Vfp9.exe that you find in the IDE's Home() folder?
> >
> >
> >
> >
> > You can put "YourProject".EXE anywhere, the folder does not matter (unless your self-made code contains hard-coded paths, not recommended).
> >
> > "Set Path" depends on your project structure, so you as the author would need to guide yourself -
> > for example, assumed you have all your project-member code files (PRGs, VCXes, SCXes, FRXes, whatever) included (default behavior of the Project Manager unless you explicitly exclude files),
> > then you would not need any Set Path statement in many cases.
> >
> > "Set Path" is only required if there are external files being required by your code, for example -
> > something like a shared Data folder if your project uses a DBC/DBF back-end, or perhaps your code wants to use some FLL like "foxtools" or so, or an OCX and so forth
> >
> >
> >
> >
> > hth
> > -Stefan
> Thanx for your very informative explanation
> One thing more to understand
> You said that on workstation copy MyProj.Exe BUT anywhere
> 1st i tell you how i set my default path setting in Main.Prg
STORE SYS(5)+'\'+SYS(2003) TO gcAppPath
> SET DEFAULT TO (gcAppPath)
> SET PATH TO	'Data;Images;Apps'


The Sys(16, 0) suggestion is safer
(because Sys(5) + Sys(2003) or FullPath(CurDir()) and so forth all just return the current directory, which is not necessarily the one where your.EXE is located, because at start-up it can be altered by something like an unexpected "Start in" property of a desktop shortcut).

> On Every Workstation 1st Mapped the Server Drive e.g. D: Drive As Z: Drive in WorkStation

Then I do not understand the SET PATH TO 'Data;Images;Apps' in the previous paragraph, wouldn't it be "Z:\Data;Images;Apps" or so?
Personally I do not use that "mapped drives" feature in application code because it is less straight-forward than a real UNC path and requires additional setup effort

> Guide where i have to copy MyProj.Exe in Workstation for better speed at WS

It does not matter
(at least not noticeably with modern hardware usually, as opposed to old-times slow HDDs vs "RAM disks" in some particular cases decades ago)



Slow Work Posted by sandeep singh @ 12/25/2013 2:37:10 PM
RE: Slow Work Posted by Pete Sass @ 12/25/2013 5:38:47 PM
RE: Slow Work Posted by Khurram Tahir @ 12/27/2013 8:01:45 AM
RE: Slow Work Posted by Stefan Wuebbe @ 12/27/2013 8:32:05 AM
RE: Slow Work Posted by Khurram Tahir @ 12/27/2013 8:47:33 AM
RE: Slow Work Posted by Stefan Wuebbe @ 12/27/2013 9:37:17 AM