Re: DEO execution sequence

Frank J. Polan wrote:
> Startup.EXE on pc
> 	function a
> 	function b
> 	function c
> 
> DEO objects on server
> 	startup.PRO
> 		function a
> 		function BB <--- note difference
> 		function c
> 
> Questions
> 
> When the app starts how much of the startup.exe will be processed
> before going to the DEO folder
> 	is the startup.PRO ignored
> 	is it copied to the PC overwriting the EXE in memory
> 	or ???

If the STARTUP.PRO is the program that becomes the .exe, then it should 
be ignored by the .EXE. They're the same thing, and you're running the 
.EXE already ...

Ken

-- 
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm

Startup.EXE on pc
	function a
	function b
	function c

DEO objects on server
	startup.PRO
		function a
		function BB <--- note difference
		function c

Questions

When the app starts how much of the startup.exe will be processed
before going to the DEO folder
	is the startup.PRO ignored
	is it copied to the PC overwriting the EXE in memory
	or ???

I'm going to try to do some tests on it this week but I'd appreciate
any comments or suggestions

Thanks

Frank Polan

Ken,

The Startup.exe and starup.pro are the same program - _except_  I
modified  the program, (note I marked the functions)  recompiled it
and uploaded it to the DEO folder. But I forgot to rebuild and copy
the EXE to the execution folder

So the app shouldn't see the changes - correct?

Thanks

Frank Polan

On Thu, 10 Apr 2008 06:32:57 -0700, "Ken Mayer [dBVIPS]"
<dbase@_nospam_goldenstag.net> wrote:

>Frank J. Polan wrote:
>> Startup.EXE on pc
>> 	function a
>> 	function b
>> 	function c
>> 
>> DEO objects on server
>> 	startup.PRO
>> 		function a
>> 		function BB <--- note difference
>> 		function c
>> 
>> Questions
>> 
>> When the app starts how much of the startup.exe will be processed
>> before going to the DEO folder
>> 	is the startup.PRO ignored
>> 	is it copied to the PC overwriting the EXE in memory
>> 	or ???
>
>If the STARTUP.PRO is the program that becomes the .exe, then it should 
>be ignored by the .EXE. They're the same thing, and you're running the 
>.EXE already ...
>
>Ken

In article <tl7sv35tf51jl7fchum7g8uudn703mtpdl@4ax.com>, 
fpolan@pcassist.on.ca says...
> Ken,
> 
> The Startup.exe and starup.pro are the same program - _except_  I
> modified  the program, (note I marked the functions)  recompiled it
> and uploaded it to the DEO folder. But I forgot to rebuild and copy
> the EXE to the execution folder
> 
> So the app shouldn't see the changes - correct?
> 
> Thanks
> 
> Frank Polan

Frank,

Yes, that sounds correct if I understand you correctly. If you make 
setup.exe (and its setup.prg) a plain program which calls 
startupMain.prg (say). You can put functions A, B, C in startupMain.prg 
and switch the startupMain.pro files to get an instantaneous update 
without having to make a new setup.exe.

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.

Ken,

Welcome back. Did you have a good trip?

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.