Error opening exe

I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and built a
new.exe. When I run new.exe I get an the error Window 'command' has not been
defined.
I can click ignore, the main menu runs but it then claims my files are
corrupt (which they are not because I checked them).

Mark
Fri Feb 11 14:22:19 CST 2005

I am afraid you are in for much more than you bargained for. I do not know
of anyone who just converted a 2.x app to a VFP app. Everyone I know of has
just re-written the app in VFP from scratch. You really should trying
running your converted forms from the VFP command window first to make sure
they work as expected.

As for your error, it looks like you are trying to show or activate a window
named Command which would be the VFP command window. If this is your own
command window, you should name it something else like cmdWindow.

"Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
> I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and built
a
> new.exe. When I run new.exe I get an the error Window 'command' has not
been
> defined.
> I can click ignore, the main menu runs but it then claims my files are
> corrupt (which they are not because I checked them).
>
>

CarolCrow
Fri Feb 11 14:39:12 CST 2005

Thanks for the tip - I have converted the screens and everything is working
as expected - I had a few bumps but it works.
Regarding the 'command' not defined - where would I define the Window.
Could the problem stem from when I build the exe? I'm a novice with this - I
need real specific help.

"Mark McCasland" wrote:

> I am afraid you are in for much more than you bargained for. I do not know
> of anyone who just converted a 2.x app to a VFP app. Everyone I know of has
> just re-written the app in VFP from scratch. You really should trying
> running your converted forms from the VFP command window first to make sure
> they work as expected.
>
> As for your error, it looks like you are trying to show or activate a window
> named Command which would be the VFP command window. If this is your own
> command window, you should name it something else like cmdWindow.
>
> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
> > I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and built
> a
> > new.exe. When I run new.exe I get an the error Window 'command' has not
> been
> > defined.
> > I can click ignore, the main menu runs but it then claims my files are
> > corrupt (which they are not because I checked them).
> >
> >
>
>
>

Rick
Fri Feb 11 14:51:47 CST 2005

Carol,
I'd start by using the Code References tool and locate the exact code =
that's referring to Command. If you post that, there many be some more =
specific recomendations on how to fix the problem.

Rick

"Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message =
news:0A1A29DE-1A07-4F27-9CFF-12DD0EFB409E@microsoft.com...
> Thanks for the tip - I have converted the screens and everything is =
working=20
> as expected - I had a few bumps but it works.=20
> Regarding the 'command' not defined - where would I define the =
Window.=20
> Could the problem stem from when I build the exe? I'm a novice with =
this - I=20
> need real specific help.
>=20
> "Mark McCasland" wrote:
>=20
>> I am afraid you are in for much more than you bargained for. I do not =
know
>> of anyone who just converted a 2.x app to a VFP app. Everyone I know =
of has
>> just re-written the app in VFP from scratch. You really should trying
>> running your converted forms from the VFP command window first to =
make sure
>> they work as expected.
>>=20
>> As for your error, it looks like you are trying to show or activate a =
window
>> named Command which would be the VFP command window. If this is your =
own
>> command window, you should name it something else like cmdWindow.
>>=20
>> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
>> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
>> > I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and =
built
>> a
>> > new.exe. When I run new.exe I get an the error Window 'command' =
has not
>> been
>> > defined.
>> > I can click ignore, the main menu runs but it then claims my files =
are
>> > corrupt (which they are not because I checked them).
>> >
>> >
>>=20
>>=20
>>

CarolCrow
Fri Feb 11 15:43:05 CST 2005

Looking thru the Code Reference tool I typed in COMMAND and 3 files in
particular appear. The Main.prg includes
Activate Window Command but that is only if it is the development version is
in use however it is at the end of all the proceedures which is when the
error shows.
What do I do now?


"Rick Bean" wrote:

> Carol,
> I'd start by using the Code References tool and locate the exact code that's referring to Command. If you post that, there many be some more specific recomendations on how to fix the problem.
>
> Rick
>
> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message news:0A1A29DE-1A07-4F27-9CFF-12DD0EFB409E@microsoft.com...
> > Thanks for the tip - I have converted the screens and everything is working
> > as expected - I had a few bumps but it works.
> > Regarding the 'command' not defined - where would I define the Window.
> > Could the problem stem from when I build the exe? I'm a novice with this - I
> > need real specific help.
> >
> > "Mark McCasland" wrote:
> >
> >> I am afraid you are in for much more than you bargained for. I do not know
> >> of anyone who just converted a 2.x app to a VFP app. Everyone I know of has
> >> just re-written the app in VFP from scratch. You really should trying
> >> running your converted forms from the VFP command window first to make sure
> >> they work as expected.
> >>
> >> As for your error, it looks like you are trying to show or activate a window
> >> named Command which would be the VFP command window. If this is your own
> >> command window, you should name it something else like cmdWindow.
> >>
> >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
> >> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
> >> > I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and built
> >> a
> >> > new.exe. When I run new.exe I get an the error Window 'command' has not
> >> been
> >> > defined.
> >> > I can click ignore, the main menu runs but it then claims my files are
> >> > corrupt (which they are not because I checked them).
> >> >
> >> >
> >>
> >>
> >>
>

Dan
Fri Feb 11 15:45:26 CST 2005

I agree with Rick. Code references is your best tool for this.

Putting on the way-back hat, many inexperienced FP2.x developers mistakenly
issued HIDE WINDOW COMMAND thinking they needed to get rid of the command
window in a runtime app. (There is no command window in a runtime app. <g>)
There was even a (erroneous) knowledgebase article advising people to do so
for a while.

You might look for that.

Dan

Carol Crow wrote:
> Thanks for the tip - I have converted the screens and everything is
> working as expected - I had a few bumps but it works.
> Regarding the 'command' not defined - where would I define the
> Window. Could the problem stem from when I build the exe? I'm a
> novice with this - I need real specific help.
>
> "Mark McCasland" wrote:
>
>> I am afraid you are in for much more than you bargained for. I do
>> not know of anyone who just converted a 2.x app to a VFP app.
>> Everyone I know of has just re-written the app in VFP from scratch.
>> You really should trying running your converted forms from the VFP
>> command window first to make sure they work as expected.
>>
>> As for your error, it looks like you are trying to show or activate
>> a window named Command which would be the VFP command window. If
>> this is your own command window, you should name it something else
>> like cmdWindow.
>>
>> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
>> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
>>> I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and
>>> built a new.exe. When I run new.exe I get an the error Window
>>> 'command' has not been defined.
>>> I can click ignore, the main menu runs but it then claims my files
>>> are corrupt (which they are not because I checked them).

Edhy
Fri Feb 11 16:18:26 CST 2005

Hi Carol,

Just comment out this code and try again.

--
Edhy Rijo
www.progytech.com
Bronx NY


"Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
news:AA12956C-750A-44CC-85DD-9B27EDC6F073@microsoft.com...
> Looking thru the Code Reference tool I typed in COMMAND and 3 files in
> particular appear. The Main.prg includes
> Activate Window Command but that is only if it is the development version
> is
> in use however it is at the end of all the proceedures which is when the
> error shows.
> What do I do now?
>
>
> "Rick Bean" wrote:
>
>> Carol,
>> I'd start by using the Code References tool and locate the exact code
>> that's referring to Command. If you post that, there many be some more
>> specific recomendations on how to fix the problem.
>>
>> Rick
>>
>> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
>> news:0A1A29DE-1A07-4F27-9CFF-12DD0EFB409E@microsoft.com...
>> > Thanks for the tip - I have converted the screens and everything is
>> > working
>> > as expected - I had a few bumps but it works.
>> > Regarding the 'command' not defined - where would I define the Window.
>> > Could the problem stem from when I build the exe? I'm a novice with
>> > this - I
>> > need real specific help.
>> >
>> > "Mark McCasland" wrote:
>> >
>> >> I am afraid you are in for much more than you bargained for. I do not
>> >> know
>> >> of anyone who just converted a 2.x app to a VFP app. Everyone I know
>> >> of has
>> >> just re-written the app in VFP from scratch. You really should trying
>> >> running your converted forms from the VFP command window first to make
>> >> sure
>> >> they work as expected.
>> >>
>> >> As for your error, it looks like you are trying to show or activate a
>> >> window
>> >> named Command which would be the VFP command window. If this is your
>> >> own
>> >> command window, you should name it something else like cmdWindow.
>> >>
>> >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
>> >> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
>> >> > I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and
>> >> > built
>> >> a
>> >> > new.exe. When I run new.exe I get an the error Window 'command' has
>> >> > not
>> >> been
>> >> > defined.
>> >> > I can click ignore, the main menu runs but it then claims my files
>> >> > are
>> >> > corrupt (which they are not because I checked them).
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>

CarolCrow
Fri Feb 11 18:37:05 CST 2005

I see where the command window is called but if I*** it out then the program
misbehavies. --And I do see a HIDE WINDOW COMMAND.
How do I work around this?


"Dan Freeman" wrote:

> I agree with Rick. Code references is your best tool for this.
>
> Putting on the way-back hat, many inexperienced FP2.x developers mistakenly
> issued HIDE WINDOW COMMAND thinking they needed to get rid of the command
> window in a runtime app. (There is no command window in a runtime app. <g>)
> There was even a (erroneous) knowledgebase article advising people to do so
> for a while.
>
> You might look for that.
>
> Dan
>
> Carol Crow wrote:
> > Thanks for the tip - I have converted the screens and everything is
> > working as expected - I had a few bumps but it works.
> > Regarding the 'command' not defined - where would I define the
> > Window. Could the problem stem from when I build the exe? I'm a
> > novice with this - I need real specific help.
> >
> > "Mark McCasland" wrote:
> >
> >> I am afraid you are in for much more than you bargained for. I do
> >> not know of anyone who just converted a 2.x app to a VFP app.
> >> Everyone I know of has just re-written the app in VFP from scratch.
> >> You really should trying running your converted forms from the VFP
> >> command window first to make sure they work as expected.
> >>
> >> As for your error, it looks like you are trying to show or activate
> >> a window named Command which would be the VFP command window. If
> >> this is your own command window, you should name it something else
> >> like cmdWindow.
> >>
> >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
> >> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
> >>> I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and
> >>> built a new.exe. When I run new.exe I get an the error Window
> >>> 'command' has not been defined.
> >>> I can click ignore, the main menu runs but it then claims my files
> >>> are corrupt (which they are not because I checked them).
>
>
>

Mark
Fri Feb 11 21:52:01 CST 2005

Can you post the code? Include a few lines before these "Command" lines and
a few lines of code after them. Try to include any lines of code around
these "command" lines that you think are important. I can not imagine anyone
needing such lines in an app.

"Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
news:D5851695-02E5-4010-ADA9-D6E00E98393D@microsoft.com...
> I see where the command window is called but if I*** it out then the
program
> misbehavies. --And I do see a HIDE WINDOW COMMAND.
> How do I work around this?
>
>
> "Dan Freeman" wrote:
>
> > I agree with Rick. Code references is your best tool for this.
> >
> > Putting on the way-back hat, many inexperienced FP2.x developers
mistakenly
> > issued HIDE WINDOW COMMAND thinking they needed to get rid of the
command
> > window in a runtime app. (There is no command window in a runtime app.
<g>)
> > There was even a (erroneous) knowledgebase article advising people to do
so
> > for a while.
> >
> > You might look for that.
> >
> > Dan
> >
> > Carol Crow wrote:
> > > Thanks for the tip - I have converted the screens and everything is
> > > working as expected - I had a few bumps but it works.
> > > Regarding the 'command' not defined - where would I define the
> > > Window. Could the problem stem from when I build the exe? I'm a
> > > novice with this - I need real specific help.
> > >
> > > "Mark McCasland" wrote:
> > >
> > >> I am afraid you are in for much more than you bargained for. I do
> > >> not know of anyone who just converted a 2.x app to a VFP app.
> > >> Everyone I know of has just re-written the app in VFP from scratch.
> > >> You really should trying running your converted forms from the VFP
> > >> command window first to make sure they work as expected.
> > >>
> > >> As for your error, it looks like you are trying to show or activate
> > >> a window named Command which would be the VFP command window. If
> > >> this is your own command window, you should name it something else
> > >> like cmdWindow.
> > >>
> > >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
> > >> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
> > >>> I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and
> > >>> built a new.exe. When I run new.exe I get an the error Window
> > >>> 'command' has not been defined.
> > >>> I can click ignore, the main menu runs but it then claims my files
> > >>> are corrupt (which they are not because I checked them).
> >
> >
> >

CarolCrow
Fri Feb 11 22:55:02 CST 2005

*Main.prg_________
PROCEDURE SetForUser
..........................................................
* The password is used to determine how the environment is set.
* If it is 'MILBOURN', then the development environment is
* set; otherwise the user enviroment is set.
*...............................................................
IF _cPass == 'MILBOURN' AND _bDevelop
*
DO (_cSystem+".MPR")
DO Add2File.MPR && Adds bars to the 'FILE' pad.
DO Develop.MPR && Adds the pads of 'EDIT' and 'PROGRAM'
ACTIVATE WINDOW COMMAND
ELSE
SET SYSMENU TO
DO (_cSystem+".MPR")
* ZOOM WINDOW COMMAND MIN
DEFINE WINDOW Hide FROM 1,1 TO 3,3
ACTIVATE WINDOW COMMAND IN Hide
ENDIF

++++++++++
Flipmode.prg

IF _bDevelop && DEVELOPER MODE ;
==============
* Cancel the Event Loop.
*
CLEAR EVENTS
*
SET DEBUG ON
* Restore the command window.
ACTIVATE WINDOW Hide
ACTIVATE WINDOW COMMAND IN SCREEN
RELEASE WINDOW Hide
*
DO SetForUser IN Main
*////
IF _bChucksPC
SET HELP TO C:\VFP3\FoxHelp.HLP
ENDIF
*\\\\ -->CM (04/26/00)
*
SET ESCAPE ON
ON ERROR
ELSE && USER MODE ;
=========
*
* Hide the command window.
DEFINE WINDOW Hide FROM 1,1 TO 3,3
ACTIVATE WINDOW Command IN Hide
ACTIVATE WINDOW COMMAND BOTTOM
SET ESCAPE OFF
SET DEBUG OFF
ON ERROR DO StatLook WITH 'SEVERE',;
'Unknown error -- general error routine invoked.',&_Args
DO (_cSystem-".MPR")
READ EVENTS
ENDIF
RETURN .T.

"Mark McCasland" wrote:

> Can you post the code?(See Main.prg and Flipmode) Include a few lines before these "Command" lines and
> a few lines of code after them. Try to include any lines of code around
> these "command" lines that you think are important. I can not imagine anyone
> needing such lines in an app.
>
> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
> news:D5851695-02E5-4010-ADA9-D6E00E98393D@microsoft.com...
> > I see where the command window is called but if I*** it out then the
> program
> > misbehavies. --And I do see a HIDE WINDOW COMMAND.
> > How do I work around this?
> >
> >
> > "Dan Freeman" wrote:
> >
> > > I agree with Rick. Code references is your best tool for this.
> > >
> > > Putting on the way-back hat, many inexperienced FP2.x developers
> mistakenly
> > > issued HIDE WINDOW COMMAND thinking they needed to get rid of the
> command
> > > window in a runtime app. (There is no command window in a runtime app.
> <g>)
> > > There was even a (erroneous) knowledgebase article advising people to do
> so
> > > for a while.
> > >
> > > You might look for that.
> > >
> > > Dan
> > >
> > > Carol Crow wrote:
> > > > Thanks for the tip - I have converted the screens and everything is
> > > > working as expected - I had a few bumps but it works.
> > > > Regarding the 'command' not defined - where would I define the
> > > > Window. Could the problem stem from when I build the exe? I'm a
> > > > novice with this - I need real specific help.
> > > >
> > > > "Mark McCasland" wrote:
> > > >
> > > >> I am afraid you are in for much more than you bargained for. I do
> > > >> not know of anyone who just converted a 2.x app to a VFP app.
> > > >> Everyone I know of has just re-written the app in VFP from scratch.
> > > >> You really should trying running your converted forms from the VFP
> > > >> command window first to make sure they work as expected.
> > > >>
> > > >> As for your error, it looks like you are trying to show or activate
> > > >> a window named Command which would be the VFP command window. If
> > > >> this is your own command window, you should name it something else
> > > >> like cmdWindow.
> > > >>
> > > >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
> > > >> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
> > > >>> I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors - and
> > > >>> built a new.exe. When I run new.exe I get an the error Window
> > > >>> 'command' has not been defined.
> > > >>> I can click ignore, the main menu runs but it then claims my files
> > > >>> are corrupt (which they are not because I checked them).
> > >
> > >
> > >
>
>
>

Wolfgang
Sun Feb 13 07:00:45 CST 2005

Hi Carol!

you should comment out this line
ACTIVATE WINDOW COMMAND IN Hide
and every other command line which includes ...window command...

--


------------------------------

Mit freundlichen Güßen aus der Zigarrenstadt

Wolfgang Schmale

------------------------------------------------

"Carol Crow" <CarolCrow@discussions.microsoft.com> schrieb im Newsbeitrag
news:CB645718-5331-440F-BAB5-089DE5AF2FEA@microsoft.com...
> *Main.prg_________
> PROCEDURE SetForUser
> ..........................................................
> * The password is used to determine how the environment is set.
> * If it is 'MILBOURN', then the development environment is
> * set; otherwise the user enviroment is set.
> *...............................................................
> IF _cPass == 'MILBOURN' AND _bDevelop
> *
> DO (_cSystem+".MPR")
> DO Add2File.MPR && Adds bars to the 'FILE' pad.
> DO Develop.MPR && Adds the pads of 'EDIT' and 'PROGRAM'
> ACTIVATE WINDOW COMMAND
> ELSE
> SET SYSMENU TO
> DO (_cSystem+".MPR")
> * ZOOM WINDOW COMMAND MIN
> DEFINE WINDOW Hide FROM 1,1 TO 3,3
> ACTIVATE WINDOW COMMAND IN Hide
> ENDIF
>
> ++++++++++
> Flipmode.prg
>
> IF _bDevelop && DEVELOPER MODE ;
> ==============
> * Cancel the Event Loop.
> *
> CLEAR EVENTS
> *
> SET DEBUG ON
> * Restore the command window.
> ACTIVATE WINDOW Hide
> ACTIVATE WINDOW COMMAND IN SCREEN
> RELEASE WINDOW Hide
> *
> DO SetForUser IN Main
> *////
> IF _bChucksPC
> SET HELP TO C:\VFP3\FoxHelp.HLP
> ENDIF
> *\\\\ -->CM (04/26/00)
> *
> SET ESCAPE ON
> ON ERROR
> ELSE && USER MODE ;
> =========
> *
> * Hide the command window.
> DEFINE WINDOW Hide FROM 1,1 TO 3,3
> ACTIVATE WINDOW Command IN Hide
> ACTIVATE WINDOW COMMAND BOTTOM
> SET ESCAPE OFF
> SET DEBUG OFF
> ON ERROR DO StatLook WITH 'SEVERE',;
> 'Unknown error -- general error routine invoked.',&_Args
> DO (_cSystem-".MPR")
> READ EVENTS
> ENDIF
> RETURN .T.
>
> "Mark McCasland" wrote:
>
>> Can you post the code?(See Main.prg and Flipmode) Include a few lines
>> before these "Command" lines and
>> a few lines of code after them. Try to include any lines of code around
>> these "command" lines that you think are important. I can not imagine
>> anyone
>> needing such lines in an app.
>>
>> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
>> news:D5851695-02E5-4010-ADA9-D6E00E98393D@microsoft.com...
>> > I see where the command window is called but if I*** it out then the
>> program
>> > misbehavies. --And I do see a HIDE WINDOW COMMAND.
>> > How do I work around this?
>> >
>> >
>> > "Dan Freeman" wrote:
>> >
>> > > I agree with Rick. Code references is your best tool for this.
>> > >
>> > > Putting on the way-back hat, many inexperienced FP2.x developers
>> mistakenly
>> > > issued HIDE WINDOW COMMAND thinking they needed to get rid of the
>> command
>> > > window in a runtime app. (There is no command window in a runtime
>> > > app.
>> <g>)
>> > > There was even a (erroneous) knowledgebase article advising people to
>> > > do
>> so
>> > > for a while.
>> > >
>> > > You might look for that.
>> > >
>> > > Dan
>> > >
>> > > Carol Crow wrote:
>> > > > Thanks for the tip - I have converted the screens and everything is
>> > > > working as expected - I had a few bumps but it works.
>> > > > Regarding the 'command' not defined - where would I define the
>> > > > Window. Could the problem stem from when I build the exe? I'm a
>> > > > novice with this - I need real specific help.
>> > > >
>> > > > "Mark McCasland" wrote:
>> > > >
>> > > >> I am afraid you are in for much more than you bargained for. I do
>> > > >> not know of anyone who just converted a 2.x app to a VFP app.
>> > > >> Everyone I know of has just re-written the app in VFP from
>> > > >> scratch.
>> > > >> You really should trying running your converted forms from the VFP
>> > > >> command window first to make sure they work as expected.
>> > > >>
>> > > >> As for your error, it looks like you are trying to show or
>> > > >> activate
>> > > >> a window named Command which would be the VFP command window. If
>> > > >> this is your own command window, you should name it something else
>> > > >> like cmdWindow.
>> > > >>
>> > > >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in
>> > > >> message
>> > > >> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
>> > > >>> I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors -
>> > > >>> and
>> > > >>> built a new.exe. When I run new.exe I get an the error Window
>> > > >>> 'command' has not been defined.
>> > > >>> I can click ignore, the main menu runs but it then claims my
>> > > >>> files
>> > > >>> are corrupt (which they are not because I checked them).
>> > >
>> > >
>> > >
>>
>>
>>

Nghia
Fri Sep 30 12:03:02 CDT 2005



"Wolfgang Schmale" wrote:

> Hi Carol!
>
> you should comment out this line
> ACTIVATE WINDOW COMMAND IN Hide
> and every other command line which includes ...window command...
>
> --
>
>
> ------------------------------
>
> Mit freundlichen Gü�en aus der Zigarrenstadt
>
> Wolfgang Schmale
>
> ------------------------------------------------
>
> "Carol Crow" <CarolCrow@discussions.microsoft.com> schrieb im Newsbeitrag
> news:CB645718-5331-440F-BAB5-089DE5AF2FEA@microsoft.com...
> > *Main.prg_________
> > PROCEDURE SetForUser
> > ..........................................................
> > * The password is used to determine how the environment is set.
> > * If it is 'MILBOURN', then the development environment is
> > * set; otherwise the user enviroment is set.
> > *...............................................................
> > IF _cPass == 'MILBOURN' AND _bDevelop
> > *
> > DO (_cSystem+".MPR")
> > DO Add2File.MPR && Adds bars to the 'FILE' pad.
> > DO Develop.MPR && Adds the pads of 'EDIT' and 'PROGRAM'
> > ACTIVATE WINDOW COMMAND
> > ELSE
> > SET SYSMENU TO
> > DO (_cSystem+".MPR")
> > * ZOOM WINDOW COMMAND MIN
> > DEFINE WINDOW Hide FROM 1,1 TO 3,3
> > ACTIVATE WINDOW COMMAND IN Hide
> > ENDIF
> >
> > ++++++++++
> > Flipmode.prg
> >
> > IF _bDevelop && DEVELOPER MODE ;
> > ==============
> > * Cancel the Event Loop.
> > *
> > CLEAR EVENTS
> > *
> > SET DEBUG ON
> > * Restore the command window.
> > ACTIVATE WINDOW Hide
> > ACTIVATE WINDOW COMMAND IN SCREEN
> > RELEASE WINDOW Hide
> > *
> > DO SetForUser IN Main
> > *////
> > IF _bChucksPC
> > SET HELP TO C:\VFP3\FoxHelp.HLP
> > ENDIF
> > *\\\\ -->CM (04/26/00)
> > *
> > SET ESCAPE ON
> > ON ERROR
> > ELSE && USER MODE ;
> > =========
> > *
> > * Hide the command window.
> > DEFINE WINDOW Hide FROM 1,1 TO 3,3
> > ACTIVATE WINDOW Command IN Hide
> > ACTIVATE WINDOW COMMAND BOTTOM
> > SET ESCAPE OFF
> > SET DEBUG OFF
> > ON ERROR DO StatLook WITH 'SEVERE',;
> > 'Unknown error -- general error routine invoked.',&_Args
> > DO (_cSystem-".MPR")
> > READ EVENTS
> > ENDIF
> > RETURN .T.
> >
> > "Mark McCasland" wrote:
> >
> >> Can you post the code?(See Main.prg and Flipmode) Include a few lines
> >> before these "Command" lines and
> >> a few lines of code after them. Try to include any lines of code around
> >> these "command" lines that you think are important. I can not imagine
> >> anyone
> >> needing such lines in an app.
> >>
> >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in message
> >> news:D5851695-02E5-4010-ADA9-D6E00E98393D@microsoft.com...
> >> > I see where the command window is called but if I*** it out then the
> >> program
> >> > misbehavies. --And I do see a HIDE WINDOW COMMAND.
> >> > How do I work around this?
> >> >
> >> >
> >> > "Dan Freeman" wrote:
> >> >
> >> > > I agree with Rick. Code references is your best tool for this.
> >> > >
> >> > > Putting on the way-back hat, many inexperienced FP2.x developers
> >> mistakenly
> >> > > issued HIDE WINDOW COMMAND thinking they needed to get rid of the
> >> command
> >> > > window in a runtime app. (There is no command window in a runtime
> >> > > app.
> >> <g>)
> >> > > There was even a (erroneous) knowledgebase article advising people to
> >> > > do
> >> so
> >> > > for a while.
> >> > >
> >> > > You might look for that.
> >> > >
> >> > > Dan
> >> > >
> >> > > Carol Crow wrote:
> >> > > > Thanks for the tip - I have converted the screens and everything is
> >> > > > working as expected - I had a few bumps but it works.
> >> > > > Regarding the 'command' not defined - where would I define the
> >> > > > Window. Could the problem stem from when I build the exe? I'm a
> >> > > > novice with this - I need real specific help.
> >> > > >
> >> > > > "Mark McCasland" wrote:
> >> > > >
> >> > > >> I am afraid you are in for much more than you bargained for. I do
> >> > > >> not know of anyone who just converted a 2.x app to a VFP app.
> >> > > >> Everyone I know of has just re-written the app in VFP from
> >> > > >> scratch.
> >> > > >> You really should trying running your converted forms from the VFP
> >> > > >> command window first to make sure they work as expected.
> >> > > >>
> >> > > >> As for your error, it looks like you are trying to show or
> >> > > >> activate
> >> > > >> a window named Command which would be the VFP command window. If
> >> > > >> this is your own command window, you should name it something else
> >> > > >> like cmdWindow.
> >> > > >>
> >> > > >> "Carol Crow" <CarolCrow@discussions.microsoft.com> wrote in
> >> > > >> message
> >> > > >> news:AC6B4F32-09A3-43D1-AFA0-5998196A6FA7@microsoft.com...
> >> > > >>> I'm upgrading vfp 2.x to vfp 9. I fixed all compiling errors -
> >> > > >>> and
> >> > > >>> built a new.exe. When I run new.exe I get an the error Window
> >> > > >>> 'command' has not been defined.
> >> > > >>> I can click ignore, the main menu runs but it then claims my
> >> > > >>> files
> >> > > >>> are corrupt (which they are not because I checked them).
> >> > >
> >> > >
> >> > >
> >>
> >>
> >>
>
>
>