Re: C5 woes. How stable is VFP really?

The machine is about 1 year old, plenty of RAM.

I rewrote one statement that pulls stuff from SQL Server.
Instead of using the plain old result-cursor, I'm appending to an explicitly created table.
After that I close the SQL server cursor and work with my manual cursor instead. This avoids keeping some SQL Server cursor open for hours. It should be a read-only cursor though, so I don't really understand why it seems to work.
It's been stable now for 3 days

Robert

"Claude Fox" <claude.fox@xxxxxxxxxxxxx> wrote in message news:eF$3xVaXHHA.4220@xxxxxxxxxxxxxxxxxxxxxxx
What kind PCs are you running the vfp apps on? I've noticed that if you run
a VFP9 app on a really old machine (old processor, not much memory) that you
may get this sort of thing. And the same would go for .NET which would,
more than likely, be more of a hog and experience the same or more problems
on low end machines .....

"RobertVanGeel" <robert@xxxxxxx> wrote in message
news:%23eSmx11WHHA.2212@xxxxxxxxxxxxxxxxxxxxxxx
I think C# could be great, but there's 5 to 6 manyears of work in this.

Thanks for your reply, I guess one day I'll have to go with your solution
anyway.

PS I'd already implemented the auto-restarter but still this does not
prevent all errors.

Robert

"Ginger Estherskip" <barkly@xxxxxxxxx> wrote in message
news:ODzFen1WHHA.4844@xxxxxxxxxxxxxxxxxxxxxxx
I still support a VFP app that I wrote...But as user demands grew and the
app was under more "pressure" (i.e. way more transactions), VFP showed
more
and more problems. So when I did the rewrite of that app I used C# using
SQL Express as the backend. Night and day difference. I hated C# at
first,
but once you get used to it, the stability, scalability, data integrity,
etc. win you over big time. And I realized I was afraid of change and
that's what held me back at first. But when you write an app in C# and
use
technologies like ClickOnce and the .NET framework and realize that the
app
works on Vista, XP x64, XP, 2000 and also runs with limited privileges and
requires like 1/10 the support time because the UI looks just like every
other windows app ... sweet. Hard at first, but once you get rolling your
productivity can be high or higher in C#. Not at first mind you, but over
time.

Best of luck with your issues... btw, my workaround to VFP blowing up was
to
have the app autorestart itself when idle after a certain amount of time.
No, I'm not kidding. It looked strange, but it did fix the C5 crashes for
the most part.


"RobertVanGeel" <robert@xxxxxxx> wrote in message
news:OJJHaP1WHHA.4632@xxxxxxxxxxxxxxxxxxxxxxx
I'm having these C5 crashes, on multiple machines. It occurs once in about
10.000 times a certain piece of code runs, sometimes I don't experience it
in days, sometimes multiple times per day.

Often it occurs in this code in a function called CloseTable:

lnSelect = Select(lcAliasName)
If lnSelect > 0
Use in (lnSelect) <-- this is the problematic statement
EndIf
I've reworked it in several ways, eg:
If Used(lcAliasName)
Use in (lcAliasName) <-- still this bugger
EndIf

I've gone over all the usual suspects: indices (dropped them, re-created
them, dropped them again etc.), foxuser.dbf, removed all printer drivers,
changed a switch, created my project again, completely re-created my prg
file, packed all my vcx and scx files, manually removed all compiled code
from all my project and did re-compiles etc..

The only thing special is that my code creates a lot of cursors and issues
use-again's on them. During a timer event (once in a minute) it flushes
certain cursors, trying to close them with the code in question.

Now, I can understand that crappy hardware or software can cause problems
but why does Word keep running, and Excel, and whatever other pogram
except
VFP? imho msft can't keep blaming this on VFP when all other stuff runs
all
right.

Thruth is, I've got big steaks in this application (basically my career),
I've been using foxpro since 2.5 and I'm starting to lose my faith that
this
is really a stable programming environment. I'm using VFP9sp1 on a couple
of
windows 2003 servers.

My question is: how stable is VFP really, what is your experience? I've
seen
quite a few posts here and there about these C5 errors, are we just coping
with them or are they really an exception?

Robert




.

Relevant Pages

  • Re: VFP View Question
    ... I am writing a VB app against a SQL Server that is shared with a VFP ...
    (microsoft.public.fox.programmer.exchange)
  • Re: VFP View Question
    ... Just like an ADO object in your app is temporary and only available in your ... you need to requery your ADO object to get the latest data, the VFP view ... >I am writing a VB app against a SQL Server that is shared with a VFP> application. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Foxpro now an "A" language
    ... Comparing SQL Server and VFP ... designing a large app in C# is not "more complex" than the same ... Performance of connection to SQL Server is FASTER than VFP is ...
    (microsoft.public.fox.programmer.exchange)
  • Re: vb or vfp: advice needed
    ... app in VFP. ... I'm also recommending for now we continue use of VFP tables for this largest ... This will probably mean a conversion to SQL server for this large critical ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Why?
    ... The temporary cursor is, sort of, a permanent dbf. ... When you retrieve the data from the SQL server into your local cursor, ... you can tell VFP to not remove the temporary cursor. ...
    (microsoft.public.fox.programmer.exchange)