Problem with PRG Shortcut or Startup Flags??? 1

[jmeckley]

I created a report in fp2.5 that queries on 7 tables. To access the report I created a program file to ask the user for input (view/print and date) before running the report.

The report runs fine if I access the process this way
1. Click Run>Application
2. select my PRG file
3. enter date
4. view/print report

For end users we would like to use a shortcut to the prg file so they do not have to know all the fox pro commands.
I have a shortcut with the following target:
c:/foxpro/foxpro.exe c:/obams/obams.prg-T
When I run this the prg runs, but when it attempts to open the report foxpro has a fatal error and crashes. I have tried this without the -T flag as well with the same fatal results.

I am a novice with foxpro 2.5 (or any foxpro for that matter) I don't know what the -T flag means. This came from another shortcut to a foxpro app that I used as a template.

So I have 2 questions:
1. why does fox pro crash when we access the report from a shortcut?
2. Is there a reference site for the different foxpro flags?

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[fitedgar]

-t suppesses the fox pro start up window.

try: c:\foxpro\foxpro.exe c:\obams\obams.prg -T

make sure the start in: is c:/obams

regards,
EMC

 

[brigmar]

-T suppresses the startup splash screen, that's all.

 

[brigmar]

As to why you're falling over, it looks like the shortcut doesn't have the correct 'startup directory' set.

Try setting it (right click the shortcut, properties, 'start in') to the same directory that the PRG is in (c:\obams)

 

[jmeckley]

I made the changes but the same problem exists. I'm leaning towards a memmory allocation issue. I ran DrWatson.exe (Win98) and it returned a more descriptive message.
[tt]
<unknown> used an uninitialized variable, attempted to access memory or a DLL that has been freed, or encountered some other nonspecific error.
[/tt]
This error also seems to relate to more than just FoxPro. It seems like it's more of a Win98 issue then a FP issue.

Is there a way to allocate more memory to a process in Win98?

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[teresas]

Is there a way to allocate more memory to a process in Win98?

Jason,

Sometimes what seems like a "not enough memory" problem is actually a "too much memory" problem. Try searching for "MEMLIMIT" in this forum. Here's one thread I found that might help (scroll to the bottom): thread182-776091

Teresa

 

[jmeckley]

from the linked post above

Either limit it in your Properties, or insert the following line in your CONFIG.FP file:

MEMLIMIT=60,2048,15360

Make sure you have the following clause in your CONFIG.SYS file:

set foxprocfg=c:\fp\config\config.fp

If you don't limit memory in FPD, it'll try to suck every byte of memory from the machine for its use, effectively slowing it down dramatically. FPD (FOXPROX)is very happy with 16mb of RAM, and standard versions (FOXPRO) needs much less than this.

I set my memory this solves the report problem, but now the system is crashing in other parts of the system that it did not used to crash.

What number would I need to increase the memory to:
32 megs?
64 megs?
96 megs?
128 megs?

This is definately the right direction I need to be going. thank you.

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[jmeckley]

I found a post at

http://fox.wikis.com/wc.dll?Wiki~Fpd26OnWin2000~VFP

on the topic.
memlimit=<percent>,<min>,<max>
It was just simple math after that.

Jason Meckley
Programmer
Specialty Bakers, Inc.

 

[teresas]

Jason,

Sounds like you got things working. What values did you decide to use for your memlimit statement? Something different than MEMLIMIT=60,2048,15360?)

Thanks for the star!

Teresa

 

[jmeckley]

memlimit=60,4096,32768

Jason Meckley
Programmer
Specialty Bakers, Inc.