Exe Problem

I just compiled my project into an .exe with vfp9/sp1. I installed it on a
server. The application runs fine on that box. However, I wish to run the
application on the workstations. I map the network drive on the workstation
and place a shortcut on its desktop which points to the .exe on the server
and the working folder is the same as the .exe on the mapped drive. When I
click on the shortcut on the workstation, it just beeps at me. Clicking on
the .exe in Windows Explorer produces the same results (or should I say,
non-results). What am I doing wrong? Is there something more that I need to
do at the workstation level?

Rick

Paul
Fri Jan 27 13:15:47 CST 2006

You must have the VFP runtimes installed on the workstations. And since
you're going to do that, might as well install the whole application.


"Rick Gangwisch" <RickGangwisch@discussions.microsoft.com> wrote in message
news:FE8358CE-E590-404E-BD7A-1A70DB1CAA6C@microsoft.com...
>I just compiled my project into an .exe with vfp9/sp1. I installed it on a
> server. The application runs fine on that box. However, I wish to run the
> application on the workstations. I map the network drive on the
> workstation
> and place a shortcut on its desktop which points to the .exe on the server
> and the working folder is the same as the .exe on the mapped drive. When
> I
> click on the shortcut on the workstation, it just beeps at me. Clicking
> on
> the .exe in Windows Explorer produces the same results (or should I say,
> non-results). What am I doing wrong? Is there something more that I need
> to
> do at the workstation level?
>
> Rick

RickGangwisch
Fri Jan 27 13:41:08 CST 2006

Paul

Thanks for the response.

Which files would I need for the vfp runtimes?

Also, if the entire application is on the workstation, do you have any
suggestions on how to have the app point to the data on the mapped server
drive? I don't want to hard code any path info since each office that
installs the program has the ability to place the data in the directory of
their choice.

Rick

"Paul Pedersen" wrote:

> You must have the VFP runtimes installed on the workstations. And since
> you're going to do that, might as well install the whole application.
>
>
> "Rick Gangwisch" <RickGangwisch@discussions.microsoft.com> wrote in message
> news:FE8358CE-E590-404E-BD7A-1A70DB1CAA6C@microsoft.com...
> >I just compiled my project into an .exe with vfp9/sp1. I installed it on a
> > server. The application runs fine on that box. However, I wish to run the
> > application on the workstations. I map the network drive on the
> > workstation
> > and place a shortcut on its desktop which points to the .exe on the server
> > and the working folder is the same as the .exe on the mapped drive. When
> > I
> > click on the shortcut on the workstation, it just beeps at me. Clicking
> > on
> > the .exe in Windows Explorer produces the same results (or should I say,
> > non-results). What am I doing wrong? Is there something more that I need
> > to
> > do at the workstation level?
> >
> > Rick
>
>
>

Leemi
Fri Jan 27 14:05:47 CST 2006

Hi Rick:

Place the following files in the folder on the server with the EXE or place
them on each workstation:

GDIplus.dll
VFP9r.dll
VFP9renu.dll
MSVCR71.dll

If you are using SP1, the VFP9*.dll file version should be 3504.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/gp/lifeselectindex
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003



>I just compiled my project into an .exe with vfp9/sp1. I installed it on a
> server. The application runs fine on that box. However, I wish to run the
> application on the workstations. I map the network drive on the
> workstation
> and place a shortcut on its desktop which points to the .exe on the server
> and the working folder is the same as the .exe on the mapped drive. When
> I
> click on the shortcut on the workstation, it just beeps at me. Clicking
> on
> the .exe in Windows Explorer produces the same results (or should I say,
> non-results). What am I doing wrong? Is there something more that I
need
> to
> do at the workstation level?
>
> Rick

RickGangwisch
Fri Jan 27 14:51:30 CST 2006

Lee

Works like a charm!

Thanks so much!

Rick

"Lee Mitchell" wrote:

> Hi Rick:
>
> Place the following files in the folder on the server with the EXE or place
> them on each workstation:
>
> GDIplus.dll
> VFP9r.dll
> VFP9renu.dll
> MSVCR71.dll
>
> If you are using SP1, the VFP9*.dll file version should be 3504.
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
> http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/gp/lifeselectindex
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
>
>
> >I just compiled my project into an .exe with vfp9/sp1. I installed it on a
> > server. The application runs fine on that box. However, I wish to run the
> > application on the workstations. I map the network drive on the
> > workstation
> > and place a shortcut on its desktop which points to the .exe on the server
> > and the working folder is the same as the .exe on the mapped drive. When
> > I
> > click on the shortcut on the workstation, it just beeps at me. Clicking
> > on
> > the .exe in Windows Explorer produces the same results (or should I say,
> > non-results). What am I doing wrong? Is there something more that I
> need
> > to
> > do at the workstation level?
> >
> > Rick
>
>
>
>
>
>
>
>
>

Cory
Fri Mar 17 13:43:30 CST 2006

Hey Lee. What would the .dll files be for a VFP 6.0 SP5 exe be?

"Lee Mitchell" wrote:

> Hi Rick:
>
> Place the following files in the folder on the server with the EXE or place
> them on each workstation:
>
> GDIplus.dll
> VFP9r.dll
> VFP9renu.dll
> MSVCR71.dll
>
> If you are using SP1, the VFP9*.dll file version should be 3504.
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 HAS ARRIVED!! --*
> Read about all the new features of VFP9 here:
> http://msdn.microsoft.com/vfoxpro/
>
> *--Purchase VFP 9.0 here:
> http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
> 69-4500-8bf2-3f06689f4ab3&type=ovr
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/gp/lifeselectindex
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
>
>
> >I just compiled my project into an .exe with vfp9/sp1. I installed it on a
> > server. The application runs fine on that box. However, I wish to run the
> > application on the workstations. I map the network drive on the
> > workstation
> > and place a shortcut on its desktop which points to the .exe on the server
> > and the working folder is the same as the .exe on the mapped drive. When
> > I
> > click on the shortcut on the workstation, it just beeps at me. Clicking
> > on
> > the .exe in Windows Explorer produces the same results (or should I say,
> > non-results). What am I doing wrong? Is there something more that I
> need
> > to
> > do at the workstation level?
> >
> > Rick
>
>
>
>
>
>
>
>
>

Cindy
Fri Mar 17 16:18:02 CST 2006

Hi Cory,

Please see "Visual FoxPro 6.0 required run-time files"
(http://support.microsoft.com/?kbid=190869)

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com


"Cory" <Cory@discussions.microsoft.com> wrote in message
news:04D1C069-E247-42AE-A033-D49975505CB9@microsoft.com...
> Hey Lee. What would the .dll files be for a VFP 6.0 SP5 exe be?

Cory
Fri Mar 17 16:28:21 CST 2006

Thanks!

"Cindy Winegarden" wrote:

> Hi Cory,
>
> Please see "Visual FoxPro 6.0 required run-time files"
> (http://support.microsoft.com/?kbid=190869)
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy_winegarden@msn.com www.cindywinegarden.com
>
>
> "Cory" <Cory@discussions.microsoft.com> wrote in message
> news:04D1C069-E247-42AE-A033-D49975505CB9@microsoft.com...
> > Hey Lee. What would the .dll files be for a VFP 6.0 SP5 exe be?
>
>
>

Cory
Thu Mar 23 18:18:02 CST 2006

Can I just put those on the server and run the program on the server from the
workstation?

"Cindy Winegarden" wrote:

> Hi Cory,
>
> Please see "Visual FoxPro 6.0 required run-time files"
> (http://support.microsoft.com/?kbid=190869)
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy_winegarden@msn.com www.cindywinegarden.com
>
>
> "Cory" <Cory@discussions.microsoft.com> wrote in message
> news:04D1C069-E247-42AE-A033-D49975505CB9@microsoft.com...
> > Hey Lee. What would the .dll files be for a VFP 6.0 SP5 exe be?
>
>
>

Dan
Thu Mar 23 18:46:47 CST 2006

Even if you put the exe file on the server, it's still going to run in the
workstation's memory. The files need to be located on the workstation.

Dan

Cory wrote:
> Can I just put those on the server and run the program on the server
> from the workstation?
>
> "Cindy Winegarden" wrote:
>
>> Hi Cory,
>>
>> Please see "Visual FoxPro 6.0 required run-time files"
>> (http://support.microsoft.com/?kbid=190869)
>>
>> --
>> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
>> cindy_winegarden@msn.com www.cindywinegarden.com
>>
>>
>> "Cory" <Cory@discussions.microsoft.com> wrote in message
>> news:04D1C069-E247-42AE-A033-D49975505CB9@microsoft.com...
>>> Hey Lee. What would the .dll files be for a VFP 6.0 SP5 exe be?

Cindy
Sat Mar 25 20:16:05 CST 2006

Hi Cory,

You may be able to run your app this way but every time the user opens the
app everything will be copied to the workstation anyways and that will make
your app open slowly.

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com


"Cory" <Cory@discussions.microsoft.com> wrote in message
news:8DC22554-3E1D-4F8D-B4D0-B65A1A1BD0E6@microsoft.com...
> Can I just put those on the server and run the program on the server from
> the
> workstation?

Cory
Mon Mar 27 13:30:01 CST 2006

Thanks Cindy. I got it running here on a server as a test. Runs fine. Do
you know what could be keeping it from working on their system. I assume it
is permissions or some thing like that. The reason I want to keep from
loading the exe on all the workstations is that we actually update monthly
and so would require a reinstall every month on the workstations.

"Cindy Winegarden" wrote:

> Hi Cory,
>
> You may be able to run your app this way but every time the user opens the
> app everything will be copied to the workstation anyways and that will make
> your app open slowly.
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy_winegarden@msn.com www.cindywinegarden.com
>
>
> "Cory" <Cory@discussions.microsoft.com> wrote in message
> news:8DC22554-3E1D-4F8D-B4D0-B65A1A1BD0E6@microsoft.com...
> > Can I just put those on the server and run the program on the server from
> > the
> > workstation?
>
>
>

Rick
Mon Mar 27 14:40:39 CST 2006

Cory,
You can get around this (and other) problems by using a loader or launcher. See
the discussion at http://fox.wikis.com/wc.dll?Wiki~LoaderProgram~VFP for some
ideas.

Rick

"Cory" <Cory@discussions.microsoft.com> wrote in message
news:E71E5CA6-043D-444C-8442-699A0389D625@microsoft.com...
> Thanks Cindy. I got it running here on a server as a test. Runs fine. Do
> you know what could be keeping it from working on their system. I assume it
> is permissions or some thing like that. The reason I want to keep from
> loading the exe on all the workstations is that we actually update monthly
> and so would require a reinstall every month on the workstations.
>
> "Cindy Winegarden" wrote:
>
>> Hi Cory,
>>
>> You may be able to run your app this way but every time the user opens the
>> app everything will be copied to the workstation anyways and that will make
>> your app open slowly.
>>
>> --
>> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
>> cindy_winegarden@msn.com www.cindywinegarden.com
>>
>>
>> "Cory" <Cory@discussions.microsoft.com> wrote in message
>> news:8DC22554-3E1D-4F8D-B4D0-B65A1A1BD0E6@microsoft.com...
>> > Can I just put those on the server and run the program on the server from
>> > the
>> > workstation?
>>
>>
>>

W
Mon Mar 27 17:24:52 CST 2006

this is a little code that works as a loader... copy it into notepad, name
it with a .vbs ending, i.e. myexe.vbs, put it in the same workstation
directory as your exe; put a shortcut to it on your desktop, and run your
app from the shortcut.... your updated exe can reside on your server and
cRemote can point to it.

Dim oFSO,oLocal,oRemote,cExe,cLocal,cRemote,oShell,cParm
cExe = "YOUR.EXE"
cLocal = "C:\Yourfolder\"
cRemote = "Z:\"
cParm = " -CC:\Yourfolder\tsconfig.fpw"
Set oFSO = CreateObject("Scripting.FileSystemObject")
Set oShell = CreateObject("Wscript.Shell")
Set oRemote = oFSO.GetFile(cRemote & cExe)
If Not oFSO.FileExists(cLocal & cExe) then
oRemote.Copy cLocal
Else
Set oLocal = oFSO.GetFile(cLocal & cExe)
If oRemote.DateLastModified > oLocal.DateLastModified Then
oRemote.Copy cLocal
End If
End If
oShell.Run(cLocal & cExe & cParm)