App differs - runtime and development

[Alexschmidt]

Using VFP7, win 2000 and same machine for development and runtime testing. I have developed a single screen program using form builder wizard and have added the foundation class - buttons\data edit buttons. Included is a Search and a Print button. During development testing within VFP they both produce exactly what I want. Once compiled into an exe the Search presents the same dialog but with the notorious VFP screen in the background (I have got SCREEN=OFF in my config.fpw) How can I get rid of it? Secondly the Print presents a totally different dialog - requiring a filename to be specified for printing, compared to the development dialog whereby a menu is presented with options such as print preview, print to file, blah, blah. Can somebody perhaps tell what this ones problem is? Thanks.

 

[Neil Toulouse]

As regards the print opening a file dialogue, this usually indicates you have a file missing from your project.

If you hit cancel when this occurs, does the error message you receive tell you what is missing?

Neil "I like work. It fascinates me. I can sit and look at it for hours..."

 

[rgbean]

Alex,
You've run into the first truism about using any wizard generated code - you're really not sure what it's doing and when.

I'll bet if you trace the code you'll find that somewhere there is a _Screen.visible = .T. (or _VFP.visible=.T.). Is the form that's created by the Wizard even Top-Level? If it isn't, you can't simply dismiss the _Screen - you won't be able to see the form. Also if there are "sub-forms", then these will either have to be Top-Level (implying non-modal) or In Top-Level, or they also won't be seen.

Rick

 

[Alexschmidt]

Thanks Gentlemen - Fatslug, no this baby doesn't give an error message when selecting Cancel, it simply closes the file open dialog. I should mention that the Print has no connection to a file of any sorts, it (in developement )presents a table like view of the underlying table content, filtered if the search function was used prior to the Print function. You mention a possible file missing, what files would have to accompany the classes in use as a norm?

As for the form created by the wizard, it is created as In-top-level and Modeless. I had to change both properties as I use it top level and Modal else the exe terminates abruptly when executed (read events)

 

[Mike Gagnon]

Alexschmidt

as I use it top level and Modal

Putting a form as Top-Level, there is no need for Modal, since the top-level negates the Modal. Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[Neil Toulouse]

Hi Alex!

There is no 'extra' file as such but if, for example, you have not added your report form to your project before building the EXE, when you hit the print button it will ask you to locate it.

However if you are not getting an error message (file not found type of thing) then this isn't it.

Are you aware you need at least one record for VFP reports to work?

Refer to Mike Gagnon's answer to create a dummy cursor in

thread184-458047

This may fix it.

Neil "I like work. It fascinates me. I can sit and look at it for hours..."