Error Number 30 - Row or Column pos is off the screen

[jsams]

I have a FPW2.6 application that was recompiled to an EXE in VFP6.0, when I try to load a modal screen selected by button on main screen, it abends with the abover error
(and then sometimes it does not). The abending screen is quite busy with field boxes and one drop down control.

I have another application that was cloned form this same application (in FPW2.6) for a different client that was also recompiled in VFP 6.0 and is running just fine.

I have stepped into the screen in Debug and it all appears fine as its building the screen, but abends on this statement:

@ 1.438,80.000 GET which_est ;
PICTURE "@^" ;
FROM a_partcde ;
SIZE 1.533,9.000 ;
DEFAULT 1 ;
FONT "Arial", 9 ;
STYLE "B" ;
VALID _08p0hgmbp()

This is a dropdown to display a code and message. The index and array values are all valid.

I have been over the generated code in both systems trying to see "whats different" and as yet have found no red flags. Both systems have been running for several years in FPW2.6.

Have tried the EXE on a number of systems: W95 and W98, and different processors and it is not appear to be hardware induced.

Sorry for the long post but its been a bear. Anyone else been down this path? I know that a rewrite would solve it, but I am committed at this point and a rewrite is not and option. Your thoughts will be greatly appreciated. TIA.

 

[BlindPete]

I used to get this message with some converted apps too. It went away so long as the APP was run maximized. A cruddy solution but it worked. Ultimately you will need to replace all of your forms into the new format to avoid it.

Sorry there is no easy answer... just lots of work.

Pete
blindpete@mail.com

What your mother told you is true! You will go blind! (from moonshine anyway)

 

[DSummZZZ]

I have run into this problem when the user is using large fonts on their system instead of small fonts. Look at the "Settings" tab on the Display Properties dialog.

 

[dgrewe]

My run ins with this problem are the same as DSummZZZX. The problem lies in the users ability to customize the screen to 400x640 resolution and use large fonts.
BlindPete is wrong about having to convert 2.6a screens to VFP forms. I have several applications running in VFP6 and using 2.6a generate screens. As a matter of fact, I have one application I write and maintain in 2.6a code but compile and run in VFP6, (Customers request). All the databases were converted to VFP free tables so I have write the report forms in VFP.

David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644

 

[BlindPete]

I agreee the 2.6 screens can work, however they do not match the look, feel and format of other windows apps. In fact I had one client comment after conversion of system from 2.6 VFP5 say, "What is this crap, I wanted windows."

Pete
blindpete@mail.com

What your mother told you is true! You will go blind! (from moonshine anyway)

 

[jsams]

Thank you all, appreciate the responses. Questions for dgrewe: is the 400x640 a max size and problems with larger screens? Currently my "settings" are small fonts, 800x600 resolution. The main screen in the app is 487x659 and the "problem" modal screen is 415 x 567.

Our directive is also to maintain the 2.6 code, running in VFP6 with free tables.

 

[Xaplytz]

You have to translate your code to VFP6 or least VFP5
if you still run the old FPW code in VFP you might have
other problems not only with the screens.

And you will see that is faster develop a system in VFP than FPW26.

 

[DSummZZZ]

If you change your Ruler/Grid setting to Characters in the screen designer, you will see that the 415 x 567 screen is about 85 columns wide. The combo box @ /GET is starting on column 80 (@ 1.438, 80.000 GET which_est), leaving about 5 columns to draw it in. The SIZE clause is "SIZE 1.533, 9.000". That means it could overlap by 4 depending on the screen font used while creating the screen.

 

[dgrewe]

Jsams, If for some reason you are trying to maintain your FPW2.6 caode sothat it runs in both the DOS and Windows mode the answer to your question about the 400X640 as the Max screen size is corect. If it is a pure FPW application the screen size is limited to the Highest resolution that the computers running the application can handle. Something like the A chain is only as strong as it's weakest link. In FPW or any VFP you can define a window larger the the screen can display and you can write to the part of the window not displayed in the scrren. As DSummZZZ was stating you appear to have made the window to small for the font the "Weakest Link" is using. One thing you can try is to state a font and font size when you define your window. My trick is to design the screen in a 9 point font but define the window in a 8 point font.

Hope this answers your question.

David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644

 

[jsams]

Dgrewe, I am only working in the FPW mode. Will give the window and screen font size a try. So far have not realized any improvements on the problem, but really appreciate the input from you and everyone else who has responded.

 

[jsams]

Problem solved!! It was the screen font specification in several of the modal screens called from the main screen. Went thru all of them and changed the screen size as suggested and the screen corruption has disappeared! System is operating very solid now.

Again, many thanks to all who responded and to Dgrewe and DSummZZZ for the specific help that did it.