Index
1998-03-06 05:00Lim Lik Chian: app installation
1998-03-09 11:09Ed Leafe: Re: app installation
1998-04-15 11:53Michael G. Emmons : New App Compile Problems (embarassing newbie stuff)
1998-04-15 12:06Michael G. Emmons : Re: New App Compile Problems (embarassing newbie stuff)
1998-08-27 17:22Matthew L. Brazier : Adding an Internet E-Mail link to CB App
1998-08-28 13:54Bob Archer : Re: Adding an Internet E-Mail link to CB App
1998-12-06 11:27Javed Aslam : Exit from App is Bye Bye forever
1998-12-11 08:29Charles T. Blankenship : Re: Exit from App is Bye Bye forever
1999-01-06 20:09Pamela Thalacker : .App behaves differently that .prg
1999-01-07 10:33Pamela Thalacker : Re: .App behaves differently than .prg
Back to top
app installation

Author: Lim Lik Chian

Posted: 1998-03-06 05:00:38   Link

I had developed a small application using VFP 3.0. I created CDs using SETUP wizard in VFP and sent out to (Shipping) agents (not secret agent!)

in the Far East region. (By the way, I work for a major shipping line, the agents appointed in various countries handle the admin and paper work for our customers. So our customers' goods can be shipped on our vessels)

Strangely, some agents could install the app without problem. Some agent encountered problem such as "some system files were out of date or error with some system files" (not exact words, something to that effect).

some agents had problem that the setup program kept asking for disk 1 to be inserted. (The app contained on a Compact Disc!).

They installed it on WIN 95. Could it be the version problem?

Could anyone offers any clue? thanks

Regards Lim Lik Chian (Mr)

LLC

©1998 Lim Lik Chian
Back to top
Re: app installation

Author: Ed Leafe

Posted: 1998-03-09 11:09:24   Link

<FONT COLOR="#663300"><I>Strangely, some agents could install the app without problem. Some agent encountered problem such as "some system files were out of date or error with some system files" (not exact words, something to that effect). some agents had problem that the setup program kept asking for disk 1 to be inserted. (The app contained on a Compact Disc!).

They installed it on WIN 95. Could it be the version problem? Could anyone offers any clue?</I></FONT>

Sounds like they had older DLL versions of some components, or were missing some of them. I've found lots of problems installing systems which relied on ActiveX controls, since many target systems did not contain them, or contained older versions.

You may need to consider a more advanced installer than the one created by the Setup Wizard. I've heard lots of good things about InstallShield, although I haven't used it myself.

<font color="#cc0000"> ___/

/

__/

/

____/</font>

Ed Leafe

©1998 Ed Leafe
Back to top
New App Compile Problems (embarassing newbie stuff)

Author: Michael G. Emmons

Posted: 1998-04-15 11:53:19   Link

Paah. You'd think by now I would remember how to fix these problems, but my new app builds are so few and far between that I always forget by the time I'm ready to build my next app ;).

I am getting the following error when I compile my new codebook app:

Compiling d:cdbk30common30progsutility.prg

#INCLUDE 'CDBK30COMMON30INCLUDEFRAMEWRK.H'

Error in line 10: File does not exist.

The app I am trying to compile is in the d:aseball directory and codebooks is in d:cdbk30 directory. The file 'CDBK30COMMON30INCLUDEFRAMEWRK.H' does indeed exist.

Michael G. Emmons

<a href="mailto:MichaelE@flashcreative.com">MichaelE@flashcreative.com</a>

Senior Consultant

<a href="http://www.flashcreative.com" class="white" onmouseover="style.color='#00cc00'" onmouseout="style.color='#0000ff'" title="Flash Creative Management Web Site">Flash Creative Management</a>

©1998 Michael G. Emmons
Back to top
Re: New App Compile Problems (embarassing newbie stuff)

Author: Michael G. Emmons

Posted: 1998-04-15 12:06:14   Link

<I><FONT COLOR="#663300">Paah. You'd think by now I would remember how to fix these problems, but my new app builds are so few and far between that I always forget by the time I'm ready to build my next app ;).

I am getting the following error when I compile my new codebook app:

Compiling d:cdbk30common30progsutility.prg

#INCLUDE 'CDBK30COMMON30INCLUDEFRAMEWRK.H'

Error in line 10: File does not exist.

The app I am trying to compile is in the d:aseball directory and codebooks is in d:cdbk30 directory. The file 'CDBK30COMMON30INCLUDEFRAMEWRK.H' does indeed exist.

</FONT></I>

Argh! Nevermind ;). Even though I had startcb running, apparently I wasn't in the project directory. One I typed "cd d:aseball" everything worked fine. Sheesh.

Michael G. Emmons

<a href="mailto:MichaelE@flashcreative.com">MichaelE@flashcreative.com</a>

Senior Consultant

<a href="http://www.flashcreative.com" class="white" onmouseover="style.color='#00cc00'" onmouseout="style.color='#0000ff'" title="Flash Creative Management Web Site">Flash Creative Management</a>

©1998 Michael G. Emmons
Back to top
Adding an Internet E-Mail link to CB App

Author: Matthew L. Brazier

Posted: 1998-08-27 17:22:25   Link

How do I do this?

Matthew L. Brazier

Developing in VFP 5/6/7, Visual Studio 6

website: www.braziercomputerconsulting.com

email: mbrazier@braziercomputerconsulting.com

©1998 Matthew L. Brazier
Back to top
Re: Adding an Internet E-Mail link to CB App

Author: Bob Archer

Posted: 1998-08-28 13:54:47   Link

<I><FONT COLOR="#663300">How do I do this?</FONT></I>

I would say, go to www.west-wind.com and grab his free wwIPStuff class that allows you to send SMTP email. If you are trying to support MAPI or send mail with Outlook you can use the MAPI class that comes with FoxPro, or use OLE Automation for outlook.

BOb

©1998 Bob Archer
Back to top
Exit from App is Bye Bye forever

Author: Javed Aslam

Posted: 1998-12-06 11:27:54   Link

Hi,

Code in Setup.prg that is executed on Exit from the App has the following lines:

*-----------------------------------------------

*-- Cleanup after the application is terminated.

*-----------------------------------------------

_screen.MousePointer = MOUSE_DEFAULT

SET PATH TO ( lcOldPath )

RELEASE ALL EXTENDED

CLEAR ALL

IF INLIST(RIGHT(SYS(16,1), 3), "APP", "EXE")

QUIT

ENDIF

The Quit takes one out of the FoxPro completely. I suppose it may be a good thing in the case of an installed App, but in the debug mode, it should probably return the programmer to the VFP so he/she can add a few more bugs to the soup. :-)

Of course, one can always "comment" the 3 lines.

Regards

Javed

©1998 Javed Aslam
Back to top
Re: Exit from App is Bye Bye forever

Author: Charles T. Blankenship

Posted: 1998-12-11 08:29:54   Link

Hi Javed:

When I am debugging, I usually start the application off using DO STARTCB and DO MAIN. As a result, the IF statement in question prevents the QUIT from executing and I remain in VFP ready for more debugging. Do you debug by typing DO <AppName>.APP or <AppName>.EXE?

Best,

CT

<I><FONT COLOR="#663300">Hi,

Code in Setup.prg that is executed on Exit from the App has the following lines:

*-----------------------------------------------

*-- Cleanup after the application is terminated.

*-----------------------------------------------

_screen.MousePointer = MOUSE_DEFAULT

SET PATH TO ( lcOldPath )

RELEASE ALL EXTENDED

CLEAR ALL

IF INLIST(RIGHT(SYS(16,1), 3), "APP", "EXE")

QUIT

ENDIF

The Quit takes one out of the FoxPro completely. I suppose it may be a good thing in the case of an installed App, but in the debug mode, it should probably return the programmer to the VFP so he/she can add a few more bugs to the soup. :-)

Of course, one can always "comment" the 3 lines.

Regards

Javed</FONT></I>

Flash Creative Management, Inc. (FLASH)

http://www.flashcreative.com

ctb@flashcreative.com

tomandanna@erols.com

©1998 Charles T. Blankenship
Back to top
.App behaves differently that .prg

Author: Pamela Thalacker

Posted: 1999-01-06 20:09:37   Link

I am trying to move my app into a test environment. I have compiled it as an .app so that I can continue to debug while it is tested. I have suddenly developed new bugs that I am not sure how to track down.

Bug #1: When I instantiate a form that works perfectly in my development environment ny running main.prg, I get the error message that 'Alias BLOCKOUTVIEW is not found.' That makes sense because there is no alias BLOCKOUTVIEW. BLOCKOUTVIEW is the name of the cursor object that is defined in my aDataEnv.prg and the cursor alias is 'vBlockout' I have defined my bizobj.cAlias property as 'vBlockout' but when I suspend the .app at the error, I find that thisform.bizobj.cAlias = 'BlockoutView' How do I go about finding where this error is occurring?

:-) Pamela

pamela@eagle-crest.com

©1999 Pamela Thalacker
Back to top
Re: .App behaves differently than .prg

Author: Pamela Thalacker

Posted: 1999-01-07 10:33:19   Link

<I><FONT COLOR="#663300">I am trying to move my app into a test environment. I have compiled it as an .app so that I can continue to debug while it is tested. I have suddenly developed new bugs that I am not sure how to track down.

Bug #1: When I instantiate a form that works perfectly in my development environment ny running main.prg, I get the error message that 'Alias BLOCKOUTVIEW is not found.' That makes sense because there is no alias BLOCKOUTVIEW. BLOCKOUTVIEW is the name of the cursor object that is defined in my aDataEnv.prg and the cursor alias is 'vBlockout' I have defined my bizobj.cAlias property as 'vBlockout' but when I suspend the .app at the error, I find that thisform.bizobj.cAlias = 'BlockoutView' How do I go about finding where this error is occurring?</FONT></I>

In addition, when I have the application suspended, the watch window says that my bizobj does not have an oDataEnvironment property. However, eBizObj.Init has already fired and the line of code:

this.oDataEnvironment = this.oDELoader.oDataEnvironment

did not produce an error. Where could the oDataEnvironment property gone? I feel as though I am looking right at something and cannot see it.

:-) Pamela

pamela@eagle-crest.com

©1999 Pamela Thalacker