Was looking for comments and sugestions on a "sub" application to an existing application in OI. The existing app. is multiuser.

The sub application wants to be able to be single user or multi and at this time not tied into the main app. other than look and feel.

If someone has the main app. they can get the sub app or not.

Was looking for ideas and caveats to (a) having it as another application within the existing system (sysprog or main app. inheritance) (b)another mdiframe with the main app. itself.

© in a completely new license of OI.

I know some of the pros and cons but wanted to get others views.

At this point (a) would probably be the best option.

TIA

Can only comment from developing Visual Basic Systems. But generally if add ons we include the software, but set the menu option enables off. Therefore the Customer can see them but not use them. When would then provide a "key" to enable the additonal options. This way you can deploy the software once, without having to send out additional service packs.

Of course with web downloads it becomes easy, cause you allow downloads of the actual exe (still talking vb here), so that the end user thinks they are getting something additional.

View this thread on the forum...