|
|
||||
|
||||
|
|
|
|||
|
Wolfgang,
You have been away too long. Brian has formally announced the end of the product life cycle some time back. There will be no more public releases and officially, 2837 is the last supported build. However I believe you can pay $1000 per year to get maintenance fixes outside of the public build program. Very few people have taken this up because obviously, it isn't good value for money. But this is a reality. VO can do everything usually needed and what it cannot, we do in C# and bolt it on to our VO app with COM. The VO IDE still has some annoying bugs and the editor still crashes and farts about with source control. But we live with this and move on. Cheers, Geoff "dengler" <denglerw@uni-freiburg.de> wrote in message news:415sh691o87p53ah21ovr2f0v634tihj27@4ax.com: > Hi > In former days there was an announcement, that there will be a service > pack every year. Is SP4 in progress for non suscription user? > What is the actual VO build number in the suscription? > Thanks Wolfgang > > And a happy new year |
|
|||
|
Thanks
It was not clear that Brian stopped VO 2.8. I looked into his newsgroup grafx.public.announcements and didn't find anything. In this case 2836 is the last offical build and 2837 the last internal Build. And VO 2.8 is definitively dead. Thanks for the information "Geoff Schaller" <geoffx@softwarexobjectives.com.au> schrieb: >Wolfgang, > >You have been away too long. Brian has formally announced the end of the >product life cycle some time back. There will be no more public releases >and officially, 2837 is the last supported build. > >However I believe you can pay $1000 per year to get maintenance fixes >outside of the public build program. Very few people have taken this up >because obviously, it isn't good value for money. > >But this is a reality. VO can do everything usually needed and what it >cannot, we do in C# and bolt it on to our VO app with COM. The VO IDE >still has some annoying bugs and the editor still crashes and farts >about with source control. But we live with this and move on. > >Cheers, > >Geoff > > > >"dengler" <denglerw@uni-freiburg.de> wrote in message >news:415sh691o87p53ah21ovr2f0v634tihj27@4ax.com : > >> Hi >> In former days there was an announcement, that there will be a service >> pack every year. Is SP4 in progress for non suscription user? >> What is the actual VO build number in the suscription? >> Thanks Wolfgang >> >> And a happy new year |
|
|||
|
I suspect Brian's agreement with CA was that he HAD to continue and
therefore he cannot publicly declare VO dead or it triggers sunset clauses in his agreement. But he has placed several posts to this forum stating that there will be no more public releases or free patches, despite the new bugs added into 2836. He has got around this by suggesting that Vulcan is the evolution of VO and that you can pay a rather large annual fee to still get some fixes. But those I know who took up this service have not renewed because they did not get value for their money. Geoff "dengler" <denglerw@uni-freiburg.de> wrote in message news:4beuh61o7jg2kkp7eo1cs4r559qkd7f08e@4ax.com: > Thanks > It was not clear that Brian stopped VO 2.8. I looked into his > newsgroup grafx.public.announcements and didn't find anything. > > In this case 2836 is the last offical build and 2837 the last > internal Build. > > And VO 2.8 is definitively dead. > > Thanks for the information > > > "Geoff Schaller" <geoffx@softwarexobjectives.com.au> schrieb: > > > >Wolfgang, > > > >You have been away too long. Brian has formally announced the end of the > >product life cycle some time back. There will be no more public releases > >and officially, 2837 is the last supported build. > > > >However I believe you can pay $1000 per year to get maintenance fixes > >outside of the public build program. Very few people have taken this up > >because obviously, it isn't good value for money. > > > >But this is a reality. VO can do everything usually needed and what it > >cannot, we do in C# and bolt it on to our VO app with COM. The VO IDE > >still has some annoying bugs and the editor still crashes and farts > >about with source control. But we live with this and move on. > > > >Cheers, > > > >Geoff > > > > > > > >"dengler" <denglerw@uni-freiburg.de> wrote in message > >news:415sh691o87p53ah21ovr2f0v634tihj27@4ax.com : > > > > >> Hi > >> In former days there was an announcement, that there will be a service > >> pack every year. Is SP4 in progress for non suscription user? > >> What is the actual VO build number in the suscription? > >> Thanks Wolfgang > >> > >> And a happy new year |
|
|||
|
Geoff
The last build is 2837 which is Sept 2009.. so more than a year ago. Even for VOPS members there is no special VO builds... even for $1000. VOPS is only for 'Vulcaneers' at this point in time.. but one can hope maybe something may change. Phil McGuinness -- |
|
|||
|
Geoff,
I feel like we have been betrayed, especially those of us who have supported and advocated VO and Vulcan for several years. For 2 years, I have been using VB.NET, C# and ASP.NET with no regrets. I still use VO to maintain existing applications. Brian! What is wrong with issuing patches to VO? Is VO such a beast and is it really that hard of a job to issue patches? Where is the goodwill? We supported you, so support us! Just venting! I have been silent on this this but just sharing my frustration like the others. Jamal "Geoff Schaller" wrote in message news:4d1ea993$0$99369$c30e37c6@exi-reader.telstra.net... Wolfgang, You have been away too long. Brian has formally announced the end of the product life cycle some time back. There will be no more public releases and officially, 2837 is the last supported build. However I believe you can pay $1000 per year to get maintenance fixes outside of the public build program. Very few people have taken this up because obviously, it isn't good value for money. But this is a reality. VO can do everything usually needed and what it cannot, we do in C# and bolt it on to our VO app with COM. The VO IDE still has some annoying bugs and the editor still crashes and farts about with source control. But we live with this and move on. Cheers, Geoff "dengler" <denglerw@uni-freiburg.de> wrote in message news:415sh691o87p53ah21ovr2f0v634tihj27@4ax.com: > Hi > In former days there was an announcement, that there will be a service > pack every year. Is SP4 in progress for non suscription user? > What is the actual VO build number in the suscription? > Thanks Wolfgang > > And a happy new year |
|
|||
|
Jamal,
I'll take the other side: I think it's fine for VO to reach a graceful end of life. I have standardized on 2831, and it really makes life simpler for me and especially for my customers who maintain hundreds of PCs that they no longer have to update the runtime DLLs every time I issue an upgrade. Sure VO still has bugs, but each new patch seemed to bring new bugs, and at least I know the old bugs and their workarounds. Even if that wasn't the case, I'd still have to invest a lot of time in testing new builds. The new features that VO got during the last years were mainly (I assume) for Vulcan compatibility, so not all that interesting otherwise. I've moved on. You've moved on. And Grafx has moved on. I think that's ok. Ginny "Jamal" wrote in message news:ifqkod$ghe$1@news.eternal-september.org... Geoff, I feel like we have been betrayed, especially those of us who have supported and advocated VO and Vulcan for several years. For 2 years, I have been using VB.NET, C# and ASP.NET with no regrets. I still use VO to maintain existing applications. Brian! What is wrong with issuing patches to VO? Is VO such a beast and is it really that hard of a job to issue patches? Where is the goodwill? We supported you, so support us! Just venting! I have been silent on this this but just sharing my frustration like the others. Jamal "Geoff Schaller" wrote in message news:4d1ea993$0$99369$c30e37c6@exi-reader.telstra.net... Wolfgang, You have been away too long. Brian has formally announced the end of the product life cycle some time back. There will be no more public releases and officially, 2837 is the last supported build. However I believe you can pay $1000 per year to get maintenance fixes outside of the public build program. Very few people have taken this up because obviously, it isn't good value for money. But this is a reality. VO can do everything usually needed and what it cannot, we do in C# and bolt it on to our VO app with COM. The VO IDE still has some annoying bugs and the editor still crashes and farts about with source control. But we live with this and move on. Cheers, Geoff "dengler" <denglerw@uni-freiburg.de> wrote in message news:415sh691o87p53ah21ovr2f0v634tihj27@4ax.com: > Hi > In former days there was an announcement, that there will be a service > pack every year. Is SP4 in progress for non suscription user? > What is the actual VO build number in the suscription? > Thanks Wolfgang > > And a happy new year |
|
|||
|
richard.townsendrose wrote:
> > As I have said many times, VO has now got to the stage that Clipper > did - there is nothing more to be developed [apart from FINISHING off > pdf for reportpro 2 - but we all get round that with barbara's > solution or pdf995 or bullzip] > > > richard Richard or anyone else, Can you tell me more about barbara's solution for pdf in reportpro ? Dirk (Belgium) -- |
|
|||
|
Dirk,
I have sent you a private email with sample VO code and everything you need to generate a PDF from a RP report. This code uses an open source product and it is a wonderful solution that I have used for many years. Barbara > richard.townsendrose wrote: > >> >> As I have said many times, VO has now got to the stage that Clipper >> did - there is nothing more to be developed [apart from FINISHING off >> pdf for reportpro 2 - but we all get round that with barbara's >> solution or pdf995 or bullzip] >> >> >> richard > > Richard or anyone else, > > Can you tell me more about barbara's solution for pdf in reportpro ? > > Dirk (Belgium) > |
|
|||
|
Benito,
Happy to share. I have emailed to the account listed in your signature. Barbara On 1/6/2011 2:41 AM, Benito Fernández wrote: > Hi Barbara > > Would you also be so kind to sending me a copy of the code? > > Thanks in advance. > > Benito Fernández > bfernandezm at prodigy dot net dot mx > > "Barbara" escribió en el mensaje de > noticias:4d250c97$0$22168$742ec2ed@news.sonic.net. .. > > Dirk, > > I have sent you a private email with sample VO code and everything you > need to generate a PDF from a RP report. This code uses an open source > product and it is a wonderful solution that I have used for many years. > > Barbara > > >> richard.townsendrose wrote: >> >>> >>> As I have said many times, VO has now got to the stage that Clipper >>> did - there is nothing more to be developed [apart from FINISHING off >>> pdf for reportpro 2 - but we all get round that with barbara's >>> solution or pdf995 or bullzip] >>> >>> >>> richard >> >> Richard or anyone else, >> >> Can you tell me more about barbara's solution for pdf in reportpro ? >> >> Dirk (Belgium) >> > |
|
|||
|
Hi Barbara
Would you also be so kind to sending me a copy of the code? Thanks in advance. Benito Fernández bfernandezm at prodigy dot net dot mx "Barbara" escribió en el mensaje de noticias:4d250c97$0$22168$742ec2ed@news.sonic.net. .. Dirk, I have sent you a private email with sample VO code and everything you need to generate a PDF from a RP report. This code uses an open source product and it is a wonderful solution that I have used for many years. Barbara > richard.townsendrose wrote: > >> >> As I have said many times, VO has now got to the stage that Clipper >> did - there is nothing more to be developed [apart from FINISHING off >> pdf for reportpro 2 - but we all get round that with barbara's >> solution or pdf995 or bullzip] >> >> >> richard > > Richard or anyone else, > > Can you tell me more about barbara's solution for pdf in reportpro ? > > Dirk (Belgium) > |
|
|||
|
Barbara wrote:
> Dirk, > > I have sent you a private email with sample VO code and everything > you need to generate a PDF from a RP report. This code uses an open > source product and it is a wonderful solution that I have used for > many years. > > Barbara > > Barbara, I have nothing received. Please can you send it to "dirk dot herijgers at pbprojects dot be" Dirk (Belgium) -- |
|
|||
|
Barbara,
I didn't received the files, Please send it to my e-mail "bfernandezm at prodigy dot net dot mx" Thank you, Benito "Barbara" escribió en el mensaje de noticias:4d256378$0$22163$742ec2ed@news.sonic.net. .. Benito, Happy to share. I have emailed to the account listed in your signature. Barbara On 1/6/2011 2:41 AM, Benito Fernández wrote: > Hi Barbara > > Would you also be so kind to sending me a copy of the code? > > Thanks in advance. > > Benito Fernández > bfernandezm at prodigy dot net dot mx > > "Barbara" escribió en el mensaje de > noticias:4d250c97$0$22168$742ec2ed@news.sonic.net. .. > > Dirk, > > I have sent you a private email with sample VO code and everything you > need to generate a PDF from a RP report. This code uses an open source > product and it is a wonderful solution that I have used for many years. > > Barbara > > >> richard.townsendrose wrote: >> >>> >>> As I have said many times, VO has now got to the stage that Clipper >>> did - there is nothing more to be developed [apart from FINISHING off >>> pdf for reportpro 2 - but we all get round that with barbara's >>> solution or pdf995 or bullzip] >>> >>> >>> richard >> >> Richard or anyone else, >> >> Can you tell me more about barbara's solution for pdf in reportpro ? >> >> Dirk (Belgium) >> > |
|
|||
|
Benito,
I did send the email yesterday to the address you provided. I am wondering if prodigy is not allowing the email to go through with an attachment. I have seen this happen with several email servers. I sent you the body of the email without the ZIP file. Please let me know if you receive that email. I can always put the ZIP file on my website if needed. Barbara > I didn't received the files, > Please send it to my e-mail "bfernandezm at prodigy dot net dot mx" > > Thank you, > Benito > |
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|