dBase Becoming Unstable (5.6)
REHoch
5.6. While testing the apps prior to uploading them to my client, I'm
running into a number of "Internal Error: Visual dBase is becoming
unstable..." message boxes on my test machine. These errors are not
occurring on my development machine and I'm not sure how to troubleshoot
this. I guess what I really need to understand is how this unstable error
is caused. I have, by the way, seen it a number of times while developing,
and have always cleared it up by closing VdB and restarting. I'm suspecting
it's caused by either a lack of PC memory or resources.
Here are the basic specs on the PCs in question:
Development PC - Windows 95 - 32MB Ram
Test PC - Windows NT 4.0 - 24 MB Ram
Thanks in advance,
Rob Hoch
Evergreen Information Systems, Inc.
http://members.aol.com/eiscoinc/EISWelcome.htm
REHoch
Romain Strieff [TeamB] wrote in message ...
>>Any WinAPI calls used? NT does not allow any wrong buffering and coding
bugs like that.
None that I'm aware of but I'll double check. I tend to think it's a lack
of memory issue.
Rob Hoch
REHoch
Gary White wrote in message <36eecb3...@forums.borland.com>...
>Lack of resources will cause problems, but I'd be more inclined to
>make sure you have a valid INI file so that the working environment
>duplicates the development environment. Just make a copy of your
>dbasewin.ini and rename it to <your_exe_name>.INI and place it in the
>same directory as your exe.
This brings up a good question. What should be in the deployed apps .INI
file? I can't seem to find any documentation on that.
Regards,
Gary White [dBVIPS]
> This brings up a good question. What should be in the deployed apps .INI
> file? I can't seem to find any documentation on that.
Safest thing is to include pretty much everything that's in your
dbasewin/vdb ini. Some of the strangest things can jump up and bite
you. I'll give a (sorry, but somewhat long winded) example.
I recently completed an app. It was working perfectly on my
development machine. I edited the INI file and removed all the IDE
specific (I thought) stuff. Deployed the app and found that I
couldn't even launch the app without receiving an Unstable message.
The app would not run at all.
Since the app ran fine on the development machine, it reasoned that
the problem was with the INI file. I copied my vdb.ini file to
exename.ini and ran the app. It was again working fine. I started
deleting things until I again got the unstable message.
Want to guess what finally did it?
[ComponentTypes]
ComponentTypeDate=1
I had a TimeStamp field that I was morphing to show only the time
portion in a grid. The morphed value to display was naturally a
string. When the grid was instantiated, it was trying to datalink a
spinbox (the default type for a date) to the string that was returned
by the BeforeGetValue routine. Instant crash!
Some people have also reported problems if the CommandWindow section
is missing. Making sure that SET CONSOLE OFF and SET TALK OFF should
take care of that one, but you never know when you might create a
session and forget to check those.
You can probably safely remove things about the palettes and designers
and such. The key is to thoroughly test and if something works in
design, but not in the exe, look for what's missing in the ini file.
Gary White [dBVIPS]
Some dBASE Stuff at
http://www.AppTools.com/dbase
dBASE2000 News Groups at
news.dbase2000.com
Robert W. Newman
noon and 3:30pm.
--
Please edit Return Email Address before sending. Remove the word ZAP
from the address..
Bob Newman
Gary White [dBVIPS]
> I see a well-deserved [] has been appended to your signature between
> noon and 3:30pm.
Why, thank you. I was going to wait for a public announcement, but
Bowen said to go ahead and start using it. There is another well
deserved addition, but I'll let Bowen announce that, if it doesn't
show up sooner. <g>
Gary White [dBVIPS]
Some dBASE Stuff at
http://www.AppTools.com/dbase
dBASE2000 News Groups at
news://news.dbase2000.com
REHoch
Rob Hoch
Evergreen Information Systems, Inc.
P.S. [dBVIPS] = dBase Very Important Person, Smile :)?
Gary White [dBVIPS]
> Thanks for the explanation, Gary. I will look at the .INI files today.
You're welcome.
> P.S. [dBVIPS] = dBase Very Important Person, Smile :)?
dBASE Volunteer Internet Support. I'm only really important to...
wait a minute... lemme see... Never mind. <g>
Gary White [dBVIPS]
Some dBASE Stuff at
http://www.AppTools.com/dbase
Please consider moving to
dBASE2000 News Groups at
news://news.dbase2000.com
as soon as possible
Romain Strieff [TeamB]
politely paraphrased ...
>
> > P.S. [dBVIPS] = dBase Very Important Person, Smile :)?
>
> dBASE Volunteer Internet Support. I'm only really important to...
> wait a minute... lemme see... Never mind. <g>
>
--
Romain Strieff [dBVIPS]
Gary White [dBVIPS]
In my pants. <blush>
dB -> dBASE
V -> Volunteer
I -> Internet
P -> Peer
S -> Support
'course I'm new at this... gimme some time to catch on. <g>
Gary White [dBVIPS]
Some dBase stuff at:
http://www.apptools.com/dbase
Robert W. Newman
>
> On Fri, 19 Mar 1999 03:18:43 +0100, Romain Strieff [TeamB] wrote:
>
> > In article <36f16d8f...@forums.borland.com>, Gary White [dBVIPS]
> > politely paraphrased ...
> > >
> > > > P.S. [dBVIPS] = dBase Very Important Person, Smile :)?
> > >
> > > dBASE Volunteer Internet Support. I'm only really important to...
> > > wait a minute... lemme see... Never mind. <g>
> > >
> > Where's the 'P' ? <G>
>
> In my pants. <blush>
>
Vinny
56?I am not sure,but it 'd help..
Melih
REHoch wrote in message <7cm94n$4s...@forums.borland.com>...
I'm in the process of upgrading a number of applications from v 5.5 to
v
5.6. While testing the apps prior to uploading them to my client, I'm
running into a number of "Internal Error: Visual dBase is becoming
unstable..." message boxes on my test machine. These errors are not
occurring on my development machine and I'm not sure how to
troubleshoot
this. I guess what I really need to understand is how this unstable
error
is caused. I have, by the way, seen it a number of times while
developing,
and have always cleared it up by closing VdB and restarting. I'm
suspecting
it's caused by either a lack of PC memory or resources.
Here are the basic specs on the PCs in question:
Development PC - Windows 95 - 32MB Ram
Test PC - Windows NT 4.0 - 24 MB Ram
Thanks in advance,
Rob Hoch
Evergreen Information Systems, Inc.
http://members.aol.com/eiscoinc/EISWelcome.htm