I installed VFP 9 SP 2 not too long ago. Since then, I have
observed a number of crashes. SP1 was stable.

I write this as I just had to delete foxuser.* AGAIN. This time,
it was because I could not modify a table that I needed to change for
debugging. I would simply start VFP, do my normal setups, open the
table, locate the row, browse, change the value in question, save, and
BAM! C0000005 everytime!

Deleting foxuser.* got rid of the problem. Rebooting did not.

And how have your VFP 9 SP 2 experiences been? Is anyone using
it? (Is it really my turn to be bleeding edge, or is everyone else
doing fine with it?)

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

VFP 9 SP2 is not the final release. It's essentially a "preview". That's
what the CTP means.

--
Fred
Microsoft Visual FoxPro MVP


"Gene Wirchenko" <genew (AT) ocis (DOT) net> wrote

"Fred Taylor" <ftaylor (AT) mvps (DOT) org!REMOVE> wrote:

I wish Microsoft had made that clearer. I thought that the CTP
applied to Sedna.

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

Heya Gene -

A CTP is somewhere between an alpha and a beta, released to the community to
kick the tires, make comments, give feedback. Most developers would not
put it on any 'production environment' if they want to keep the integrity of
their workspace intact.

I would never put a CTP (or alpha or beta or even RC for that matter) on a
development machine that I or my staff use for real work.

So - how is the CTP SP2 working out for me ? on the alpha testing machines
we use here- it's got a few quirks .
And we've made comments back to MS. Did you make any comments back to MS
over at that 'connect' website ?

If you are still using ONE machine - I would strongly suggest you don't
install it in your 'normal working environment'.
You COULD set up a VM or even make a different boot partition for testing
(you know, W2K SP3, VFP9, Sedna CTP, the dot net runtimes, VFP 9 CTP SP2)
and then choose to boot INTO yer 'alpha testing partition'. I do stuff that
way when I get limited to one machine - hasn't happened in the last 2 years.


Good Luck, though- IFWY, I'd remove the VFP 9 CTP SP2 from your 'production
environment' entirely.
Regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

"Gene Wirchenko" <genew (AT) ocis (DOT) net> wrote

"swdev2" <wsanders (AT) dotnetconversions (DOT) bob.com> wrote:

[snip]

It is not production. It is development.

I am considering reverting. ("You hear that, Hamster?[1] Any
more trouble and VFP gets reverted. Just give me an excuse.")

[1] Hamster is the name of my 21st century computer. I was living in
Bellingham, WA when I got it, and people from Bellingham are called
"Bellinghamsters" or just "'Hamsters" or "Hamsters".

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

Sorry - I put the single quotes around it cause I don't know what *you* call
it.

I was trying to point out the machine where you do your work with VFP.

I assume my 'production machines' that we use for daily software development
work are stable because
I don't allow beta, RC, CTP or alpha versions of anything on them. I call
it production cause
thats where we 'produce' software for consumption. It's a safe assumption,
as we do checks overnight and audit
things.

But putting a beta, a RC, a CTP, an alpha version on ONE of those will make
it unstable, in some way,
shape, or fashion. I can't allow that to happen in my shop, cause then it
eats into CODING time
for the stuff we produce. Hence my label 'production machine' . I do allow
any team member to check out
another machine to do 'non-standard testing' - ie - to actually LOAD a beta,
a RC, a CTP, an alpha version
of another vendor's software or libraries, but then we get reports back on
the testing that is done as well.
We also have 'CLEAN' machines for the testing of PRODUCTION codebase prior
to final release.

I dunno. Hamster[1] should be kept clean so you can be productive and
PRODUCE codebase for
others to use, right ?

You got another technique that you utilize for testing alpha, beta, RC or
CTP versions for Hamster[1]?
I pointed to a few other ways for the 'single box developer' to make that
happen in a previous response to
this thread - but what's *YOUR* approach for Hamster[1] ? (If it's
proprietary, my apologies for asking)

But - I gotta tell you this - you're right about one big thing -
It wasn't *THAT* obvious for this combined CTP release - I had to read it a
coupla times before I sent out that
notice NOT to install it in our production machines in the developer group.

Warmest Regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

"Gene Wirchenko" <genew (AT) ocis (DOT) net> wrote