Hi Armeen,



Thank you the the reply and i like the answers :-)



3 more questions:



1. What about the permissions required to install the PB application?

Usually when installing an application in general the user logged into windows needs to be local admin.



2. In my case I have many additional files that needs to go into a number of subfolders under the main installation folder. can that be done ?



3. I have 3 ActiveX controls that should be registered. can that be done?

(Only the PB application is using the controls, so they do not need to be registered for other programs to use.)



Thanks.

// Steen



ps.

I think Appeon is really good at providing the right enhancements to PowerBuilder.

Sybase wans completely out of touch with their user base and did so little broadly useful enhancements. All that "java" and EA server "shit" was completely useless for 99% of the PB developers.

SO ... Thank you for taking so good care of PowerBuilder it is most appreciated and worth the subscription fee. (I have 2 Cloud licenses)

1. Admin rights only required to get the application updater installed and any external DLLs installed/registered.

2. Yes, you can package additional files with your app.

3. Yes, you can package and register OCX/ActiveX, but this will require user to have admin privileges.

Excellent, Thank you. Looking SO MUCH forward.

The idea is to automatically update the PB application. I think that a prompt to the user is not good and most will skip it and not get the important updates. But I dont know for sure how PowerClient manages that.



I believe you have to manage your deployments your self and give different customers different installation urls just like you would with and installation program.



Just my 2 cents :-)

Yes, the Appeon Installer will automatically handle updates. It checks each time the app is started. The user doesn't need to do anything.

There are no configurable update strategies. In future versions we will consider to give options. Please send your ideas about this to product@appeon.com so it gets considered.

It already supports multiple applications. Each application is deployed to its own folder on the Web server and is independent from the other applications deployed.

Julie, let me chip in on what Richard might say. We have an ERP for a customer that consists of 15 relatively small PowerBuilder applications (like modules). Source code is shared among applications as needed. Each has its own version and each is installed to different persons within the company; procurement, warehouse, sales, accounting, etc. They are all C/S applications connecting to the same database. All applications are used but not all users use all applications (sounds like a riddle). Each application needs to be updated automatically each time a new version of it is built and released. Based on Armeen's comment above there should be no problem with this scenario.