Re: Windows Keep Closing

Contents of the command window have nothing to do with the registry. That's
saved in a file (_command.prg, I think) in the VFP directory. Since the
installer didn't create it and it has been updated since installation, the
uninstaller can't remove it. Likewise any foxuser.* resource files or any
other files you've created in the VFP directory. You have to remove that
directory manually.

I'm still worried about the low diskspace issue you mentioned earlier (but
never responded to) and VFP's TMPFILES more than installation issues.

Dan

Jim Fuchs wrote:
Hi Dan.

I'm now here at my laptop. I completely un-installed VFP 9.0, THEN
went into RegEdit and found the existance of a VFP under Microsoft
programs, deleted it, THEN even did a defrag. I thought this got
everything. But no. When I re-installed VFP 9.0, my first suspicion
I didn't get everything was it asked me if I wanted to "Repare or
replace" VFP." Then, when I went into it the first time after
"re-installation" my Command window STILL had all my previous
commands. This told me it, somehow, was never completely
un-installed. It should have been a completely empty Command window.
I brought up an SCX Form and it's INIT page. I clicked my mouse on
the Init text, then the Command window and the entire SCX file
closed. GOD this is frustrating!

How, how can I COMPLETELY remove ANY existance of VFP for a TRUE clean
install?

Thanks AGAIN!!!

Jim Fuchs

"Dan Freeman" wrote:

Jim,

When you move around a VFP project, never rule out ANYTHING. <g>
Different drives can make VFP go bonkers (that's the technical term)
in the most unpredictable of ways.

I'm not ready to declare the laptop dead yet. (Unless you WANT a new
laptop! <g>) I'd uninstall VFP, and then manually inspect the
registry and delete any VFP key. (Uninstall leaves some flotsam
there, I think.) VFP will create any registry keys it needs when you
run it.

This is really the only way to get a clean install.

Just out of curiosity, do you have a service pack on one machine
that isn't on the other?

Also, if you are running out of room on c:, where are VFP's temp
files being written? (You can redirect this in config.fpw using the
TEMPFILES= setting.) Running out of space in temp files could also
mightily confuse VFP.

Dan


Jim Fuchs wrote:
Dan, First - thanks for sticking it out with me. When I say
"command window" I mean the FoxPro command line. If I run an .EXE
file, I'll say DO <path>myprogram.exe or something like that, but
that's not what I'm experiencing problems with.

My laptop uses Drive C and my desktop uses Drive D (no more room on
C).
When I go back and forth, I do get the question "Is blah blah blah
the new home for this program?" or something like that I can't
exactly remember the words, but you understand. My programs always
SET SAFETY OFF for variuous reasons (so as not to bother the user).

I can't believe, though, that different drive letters have anything
to do with this, though, as I first experienced this on the laptop
(Drive C) after first creating the program there and before moving
it anywhere. And I can't see the SET SAFETY as an issue, since
these weird events are occuring during development, not while
running anything.

I've since brought the project (and all associated files) over to
ANOTHER PC to try and DO NOT experience any problems. What really
bothers me is that a clean re-install of VFP 9.0 on the laptop
didn't clear up the problem. This leads me to think there's
something wrong with my laptop, not VFP. I'm wondering what
possible "things" (setings, BIOS, etc.) need to be altered on my
PC. Would you now agree with my guess that it's the laptop and not
VFP that's the problem?

Jim

"Dan Freeman" wrote:

Oh, so you used the ambiguous word "program" to mean "project and
all associated files". That's where my confusion came from. <g>

You describe "running from command line" which to me connotes a DOS
window. Why would you do that? (Nothing to do with this, I'm sure,
but I'm curious.)

The behavior you're describing is almost like what happens when you
issue BROWSE (in a program -- and I mean code by that) without
NOWAIT and click on another window, or MODI FORM (in a program --
and I mean code by that) without NOWAIT and click on another
window. Perhaps in conjunction with SET SAFETY OFF or something???

Are your drive letters and relative directories for all files in
your projects the same on your work and home PC?

This is just truly weird behavior. I've never heard of anything
like it.

Dan

Jim Fuchs wrote:
So sorry I'm not as descriptive as I should be. When I bring a
"program" home from work to my laptop, or vise-versa, I bring the
entire directory, which includes the Project, all my .PRGs, SCXs,
etc, the compiled .APP and the compiled .EXE (basically
everything I need to work on a "program").

"Programs" created on my laptop, when brought to work carry along
with them the problems exhibited on the laptop (windows closing
when you click on another - such as the form edit screen closes -
WITHOUT saving - when I click on the command window and such.)
Programs created at work are just fine, but then exhibit the
laptop phenomenon when brought to the laptop. I always compile
into .EXEs and run them from the command line and they run fine.
It's when I'm trying to EDIT things in my project that these
problems occur.

Does that help?

Thanks again.
Jim

"Dan Freeman" wrote:

Can you clarify this:

I copied the program created on my laptop

What file did you copy? Is it a program (i.e. prg file) or an
executable (i.e. exe file)? Both are program files, but you've
made it darned difficult for anyone to tell which you mean.

How are you running that file (whatever the heck it is) on the
target machine? Are you typing DO in the command window? Choosing
it in the VFP Run dialog? Double-clicking it in Windows explorer?
Somethign else? Again, you've waffled on this so I can't be sure
exactly what's going on.

Nobody can see through your eyes. We have to rely on you to tell
us EXACTLY what you're doing.

Dan


Jim Fuchs wrote:
Dan,

So sorry to confuse you. I didn't think we've determined
anything yet. I'm simply reporting on it's performance, and
still have no idea what is going on. As I see it now, anything
CREATED on the laptop is embedded with some sort of bug, and
carries itself to other computers. However, anything created
on other computers still exhibit that problem on my laptop.

Thank you for the help, though. I'll have to find another
channel for my problem I guess.

Jim

"Dan Freeman" wrote:

You've flip-flopped again. I thought we had determined that
this was happening in the VFP IDE and **NOT** in programs that
you created.

Now you're saying exactly the opposite.

I'll bow out of this since it's impossible to get an accurate
description of the problem. Sorry.

Dan

Jim Fuchs wrote:
Haven't tried the Safe Boot yet, as I'm at work. HOWEVER - I
copied the program created on my laptop to my computer here at
work (exact same VFP install) and the program brought along
the same characteristics (windows closing) as was happning on
my laptop. The programs I created here (at work) still
operate properly. Does that give anyone a clue? (something
is imbedded in the program, not a system problem?)

Jim

"Dan Freeman" wrote:

I agree with Fred. Safe mode is worth a try.

It sounds like you've got SOMETHING mucking with they
keyboard stream. It could be a systray utility or a driver
for somethingorother. Safe mode would take those things off
the table, at least.

Dan

Jim Fuchs wrote:
Did the re-install and VFPCLEAN.APP, tried the C:\Program
Files\Microsoft Visual FoxPro 9\vfp9.exe /A. No change. I
really don't want to do what Tony suggests - reinstall the
operating system. No other program gives me any trouble at
all, not MS Office stuff or anything else. No keyboard
macros running (that I',m aware of).

I'm just going to have to live with this, but also search
through my Task Manager processors for anything weird. Any
other suggestions would be greatly appreciated.

Jim

"Jim Fuchs" wrote:

I'll give it a try and let you know.
Thanks!
Jim

"Dan Freeman" wrote:

OK, so we've firmly established that this DOES NOT HAPPEN
in your applications. It happens in the VFP IDE.

After you reinstall VFP cleanly, try running VFPCLEAN.APP
which may clean up any muck in the registry. (You'll find
it in the VFP folder.)

This is extremely odd behavior that I've never seen
before. Do you have any keyboard macro utilities
installed? Do you experience similar non-normal behavior
in, say, Word or Excel?

Do you get the same result when you run <path>\VFP.EXE /A
? (see "How to: Use Command-Line Options When Starting
Visual FoxPro" in help.)

Dan

Jim Fuchs wrote:
Sorry for not being descriptive enough. The "programs" I
write are just compiled .EXE files accessing stand-alone
tables. When I "install" them at a client's site, I just
bring along the tables, the .EXE, support .DLLs and such
- I've never written a self-installation application.
What I'm referring to is, during development, I'll have
a form and its INIT function up on the screen, then when
I click on the command window, data session, or try a
"Find" in the INIT, all my form screens just close,
without saving.

I've un-installed and re-installed VFP once already, with
no change. I'm beginning to think there's something going
on with my laptop (only a year old), or when I
un-installed FoxPro it didn't completely un-install, or
there's some patch or something that needs to be added.

Does that help?
Jim Fuchs

"Dan Freeman" wrote:

No, he meant when you built the installer for your own
applications. VFP has some system dependencies that can
be at best dicey to figure out. Installers built with
Installshield Express take care of making sure the right
files are in the right place.

I've now re-read the entire thread and I *still* can't
figure out whether you're talking about VFP itself or
applications built in VFP. If it's VFP itself, have you
installed any frameworks? Some frameworks shamelessly
remap the keyboard -- one in particular traps CTRL-F and
closes the opened designer window.

A little more details and a more clear description of
what is happening might help you get to the bottom of
this.

Dan

Jim Fuchs wrote:
Both programs on the laptop do the same thing - closing
windows. When you mention "installsheild express" I
take iy you mean when I installed FoxPro to begin with
(not my own programs). If so, yes. I just used all the
defaults. I'll tell you, it's driving me mad!

Jim

"Cy Welch" wrote:

Ok, so this is not VFP that is not working but rather
a program that you wrote in VFP? Did you use the
installsheild express that came with VFP to create the
install? I find I have the best luck using that if I
get the settings right because all the right things
get installed. It sounds like something IS installed
on one machine and is NOT installed on the other.

Cy Welch
Senior Programmer
MetSYS Inc
http://www.metsysinc.com


Jim Fuchs wrote:
Same program (same disk even). I once did a complete
un-install, rebooted, then installed it again, but
the problem still continued. I went through all the
Tools / Options looking for soe kind of setting that
needed changing, but couldn't find one. Come to
think of it, I have two different programs I created
using VFP 9 and, when I get back home, I'm going to
see if the first one does the same thing. If not,
then I can narrow it down to the program. I'll let
you know tomorrow.

Thanks Cy.

"Cy Welch" wrote:

What do you mean by "similar version"? Sounds like
maybe a bad install? What version of windows on
the laptop and what version on the pc at work?
Also did you install SP1 in both places? I find
that VFP 9 works the same on my work pc and my
laptop. With the exception of visual issues, it
works the same on Vista as on XP or 2000 as well.

Cy Welch
Senior Programmer


.