When was powerbuilder 7 released

Can you clarify? Converting current code Powerbuilder 6. Hi, can anyone tell me what you have to do in order to convert existing code applications created under Powerbuilder 6. Kerstens gnb. PowerBuilder 8 vs version 7.

Is there a URL or a message here that people could point me to? We currently have a PB 5 application which is to be migrated and we're trying to decide if we want to migrate to 7 or 8. There haven't been many posts so Latest sub version of powerbuilder 7. Is it the latest version for PB7 Desktop. Check the download page for PowerBuilder at www. PowerBuilder 7. We are currently using PowerBuilder Enterprise 7. We have recently been experiencing GPFs in built versions of our application but the same application works fine when run from inside PowerBuilder's IDE.

Out of curiousity, I created a test area, copied the built application and the runtime DLLs from the build of PowerBuilder into this test area and the GPFs stopped. Web resources about - PowerBuilder 7 the last version?? It has been in use since , peaking around Sybase PowerBuilder tool readied for Microsoft's. Win32 or newer style. Net development After several years of work, Sybase is ready to deliver on the final step in its plan to move PowerBuilder Cookies help personalize Twitter content, tailor For instance, when I was in the WinRunner world there were plugins for driving terminal emulators and powerbuilder Here you will find information about Contact Us.

For more information about Business Intelligence, Mobile app security: Always keep the back door locked The best way to keep mobile apps safe is to secure the services they connect to. Java is highly popular language for writing web apps and custom enterprise apps. See related articles to this posting. The issues related to memory have been exagerrated and surface only due to bad development practices. Sybase's practice has been to end support on the second oldest version two or three months after a new version is released.

When PB 8 was released in August , they terminated support for 6. Going by those figures, support for PB 7 would go away sometime next semester this year. However, keeping the large community that is still using 7 in mind, Sybase might be forced to extend the support for some time.

Just a thought I do believe sybase will extend support if a particular project can put forward a valid business case, but done quote me on that one. But i think, normally, Sybase used to give atleast 6 month gap between the start of notice period and the support end date Warm Regards, Jyothi. RDPaul is right. Haven't heard an explicit end-of-support announcement for PB7 yet. Doesn't mean you can't use PB7 past that period. Just means you want to get migrated before you get the urge to call Sybase for help.

Don't forget you're coming to the place that people come to complain about the product If there's a release that you shouldn't worry about upgrading to, it's probably PB8.

Now, the only question should be whether to jump on PB9 or not. If PB9 is as reliable, then going PB9 will buy you an extra months until the release of PB11 instead of PB10 before the Sybase support issue will influence you to upgrade. Not that PB10 isn't going to be so fantastic that you'll want to upgrade immediately. Version 2. Why not call your Sybase Account rep. Could you please let me know how did you get that 90 days?

Thanks and Warm Regards, Jyothi. Either wait for an official announcement from Sybase or ask them directly. They make two distinct statements here. Support is continued for a minimum of one year after either the introduction of a new major version for a product or a notification of the End of Life for a product line. First, if they decide not to bring out new versions, they can still issue an E. If they only come out with one more version, they can still claim to drop T.

If you want to apply this logic to PB 7, you would count one year from when PB 8 was released, since it would be a "new major version" with respect to PB 7. After the installation completes, ensure that the corresponding PowerBuilder version is installed on PowerBuilder client machines. To run PowerBuilder components in EAServer, the runtime dynamic shared libraries for the version of PowerBuilder in which the components were developed must be available on the server.

The PowerBuilder runtime files on the client and the server must be at the same build level. Using different build levels on client and server machines may result in unpredictable behavior or data corruption.