FPW26 and WIN/2K; Can't open screen designer

[rlw1839]

I have just upgraded my laptop (winbook j1 with 254mg ram)from windows me to 2k professional; with service pack 3.

I first noticed a problem when I tried to print a report from a small fpw26 application. When I tried to execute the report I was pitched our of foxpro with no error message.

I then discovered when I tried to open the report using 'modify report' the same thing happened; pitched out without error. Then I tried to open a screen with 'modify screen' and pitched out again.

Fpw26 worked fine under windows me. Is there something in the 2k pro. configuration that's causing this?

 

[rgbean]

We've used the high-speed CPU patched version of FPW 2.6a for a number of years on NT 4.0 SP6a, W2K SP 2->4 and XP with and without SP1, and had no troubles like this.

A while back some of the viruses were attacking SCT files (thinking they were VB script files), but if you have a good virus checker that shouldn't be a problem.

Have you tried restoring the FPW files from a good backup?(Especially useful would be files from before your upgrade.)

Have you tried these screens and reports on another system?

Rick

 

[rlw1839]

I have copied the application to a windows 98 workstation and the problem does not occur. I was able to execute reports from within the application. Also reports and screens opened up when I attempted to modify them (modi screen; modi report).

I also copied the application to a windows 2k workstation at a customer site (only has sp 2 installed and less RAM; 128) and the problem does not occur.

Looks like the *.scx's and *.frx's are ok. There must be something about the 2k configuration on my laptop?? Any suggestions where to look? memory issues? When I try to edit a screen it hesitates for a couple seconds the pitches out of foxpro.

 

[OnePunchMickey]

Try restarting the problem box in Safe Mode and see what happens.

Are you logging into it as an admin-equivalent user?

Try opening the SCX as a DBF (which is what it is) and doing a PACK and REINDEX.

It's possible that the environment (i.e. open tables etc.) has been stored with the screen definition, which you should never do. Try

MODI SCREEN myscreen NOENVIRONMENT.

***************************************
Need help running those old FoxPro apps on modern systems?

http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

 

[rgbean]

One other thing I'd check is the MEMLIMIT in your CONFIG.FPW file. I've seen problems on machines with "lots" of memory. Since FoxPro DOS or Windows can't use more than 16MB, I use MEMLIMIT = 60, 2048, 16384. Note: Others have disputed these numbers, but they work for me!

Also, make sure your temp file designations in the CONFIG.FPW all point to a directory that exists and that this user has full rights to! e.g.

tmpfiles=c:\foxtemp
sortwork=c:\foxtemp
editwork=c:\foxtemp
progwork=c:\foxtemp

Rick

 

[rlw1839]

Thanks for the suggestions!!!!

I have the software for 7 different applications on my laptop with hundreds of SCX's and FRX's. The problem is not specific to any one scx or frx. I've tried to open dozen's of them across applications; in different directories. I also have several copies of my foxprow.exe on the laptop that I've used all with the same result; pause then ditch out of foxpro with no error.

I changed the memlimit setting as suggested and the problem still occurs. Openning foxpro with or without a config.fpw the result/problem is the same.

I restarted the laptop in safe mode; openned foxpro and successfully openned both screens and reports! The problem does NOT OCCUR IN SAFE MODE! What does this mean?????

 

[OnePunchMickey]

It means something that's loading when Windows starts normally is screwing it up!

Could be your graphics driver. Try knocking the graphics hardware acceleration setting in Windows back a bit (Display Properies / Settings / Advanced button / Troubleshooting) and see if that helps.


***************************************
Need help running those old FoxPro apps on modern systems?

http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

 

[rlw1839]

I tried all the levels of the hardware acceleration setting and still the problem persists.

All I have installed on the laptop besides fpw26 is Microsoft visual studio, Office pro 2k, iomega zip software, avg anti-virus software.

What other drivers could be a problem??

 

[rlw1839]

I just discovered something new. I am now at a customer site where I usually connect my laptop to the network. After connecting to the network I openned fpw26 (the .exe is on my laptop!) and successfully openned several screens and reports for editing. Foxpro did not close; the problem did not appear. I then logged off the network and tried it again as a stand alone. The problem re-appeared! In all cases I am attempting to open screens and reports that are on my laptop hard drive; the .exe is also. (when I work stand alone I am logging into to windows 2k as the administrator).

What could be happening differently on and off the network?

 

[rgbean]

AH (The light goes on!) It's CRITICAL that if there is a Virus checker running on a workstation or server that it be configured to NOT actively check standard FoxPro files (.DBF, .FPT, .CDX) and on developer systems all the other file types (e.g. .SCT, .SCX, .PJX, PJT, .FRX, .FRT, etc.).

The basic information in the following article also applies to other AV apps depending on how they are implemented and how they can be configured.

http://support.microsoft.com/default.aspx?scid=kb;en-us;321550

- "HOWTO: Optimize Visual FoxPro Applications While Using Norton AntiVirus 2002"

Rick

 

[rlw1839]

I disabled the resident shield of the AVG virus checker and the problem still occurs; can't open the screen or report editor as a stand alone; but CAN when on the network.

 

[OnePunchMickey]

Okay, open up a screen when connected to the network using:

MODIFY SCREEN myscreen NOENVIRONMENT

When you get it open, go to the Screen menu at the top and select Layout, then the Environment button. If the Clear button is lit up, press it.

The resident virus scanner will be running whether logged into the network or not so I think that's a red herring.

***************************************
Need help running those old FoxPro apps on modern systems?

http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

 

[rlw1839]

I'm able to connect to the network today so carried out the last suggestion. The clear button was disabled. I never save the environment in my screens. The issue is not about any one screen; I can either open any and all (on the network) OR none (stand alone).

 

[rlw1839]

FINALLY A SOLUTION!

Since my fpw26 was working when I was logged onto the network under my network user name I was curious what would happen if I created a user (other than administrator) on my laptop. So I created a new user; gave this user full administrator privileges; logged in and to my great pleasure FPW26 NOW OPENS THE SCREEN AND REPORT EDITOR!!! So I'm back in business with full FPW26 functionality.

The puzzle; what prevents fpw26 from openning the screen and report editors when I'm logged in as administrator and allows it to work when I'm logged in under a user that has full administrative rights????? Some configuration issues in the administrator setup???

Academic curiosity!

Thanks all for the suggestions!!