---
but I have questions about what will even have to be deployed (_reportpreview.app value?, updated dll's). Deployment for a new application is easy. It's updating that is a major issue and 1000's of us deal with that everyday
----

So go ahead and ask your questions <s>.

Obviously (or maybe not) you should count on building a setup.exe that includes the relevant files. There are some kinks to iron out here, but if this is not your current deployment strategy (yeah I know some people avoid it) it probably should be... IAC what is?

As far as what the value is to including the report*.app files, and what you need:

You want all three if you use MODI/CREATE REPORT/LABEL in your apps. Otherwise you can omit reportbuilder.app, ship just reportpreview.app and reportoutput.app.

For a base-state test, try putting both of those in the HOME() directory and adding REPORTBEHAVIOR=90 to your CONFIG.FPW. Reminder: HOME() is where the runtime is, for distributed apps.

If you want to start planning, this should give you a way to evaluate. It will not work out for every FRX without some layout adjustment (see the known issues in the release notes for information), but you'll be able to gauge the scope of any changes just by running your app in this state.

As far as additional deployment issues... are your FRXs and LBXs built in to the EXE, or do you need to distribute them separately on disk?

BTW: right now we know there are issues with Win98 and new-style reporting; it is not a permanent limitation. If you do have Win98 users, from what I understand they find new-style preview a whole lot more attractive than the old one <s>.

HTH,

>L<