I have this this problem on Win2000 only systems:
my application crashes very early at startup, I found it
doesn't crash if I:
- flag foxuser.* files as read-only
- delete foxuser.* files (but in this way it crashes next startup)

This never happened in the past and I can't find a reason.
At startup I SET RESOURCE OFF.
I changed nothing in my startup procedure.

--
Andrea Mariottini

Stefan Wuebbe wrote:

I can't use a config.fpw file because a bug I found: if I include
a fpw file in my exe then I have problems with
createobject("VisualFoxPro.Application").

If I could find the cause of this, maybe I can solve in another way...
I don't explain why this never happened before, and why only on Win2000.

--
Andrea Mariottini

Whoa! Back up! Your situation has anomaly written all over it. :-)

1. Why are you creating an instance of VisualFoxpro.Application in a runtime
app? Technically speaking, that object shouldn't be available *anyway* and
at runtime you can get a reference to the application object through _VFP.

2. What problems were you encountering? I have serious doubts that it had
anything at all to do with including a config.fpw.

3. What version of VFP?

Dan

"Andrea Mariottini" <a.mariottini (AT) libero (DOT) it> wrote

Thanks to all for the solutions proposed.
By now I think to flag the file as read-only is the better choice
because I don't have to change my code.
However I would like to understand "why" this strange behavior
(never seen before) on Win2000 systems (not all!).
I hope someone in Microsoft could reply.

--
Andrea Mariottini