Return to BSD News archive
Xref: sserve comp.os.386bsd.development:2797 comp.lang.basic.visual:27983 comp.lang.basic.visual.misc:941 comp.databases.sybase:11739 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newshost.marcam.com!news.kei.com!ddsw1!usenet From: "Raymond M. Glassmeyer" <rayg@mcs.com> Newsgroups: comp.os.386bsd.development,comp.lang.basic.visual,comp.lang.basic.visual.misc,comp.databases.sybase Subject: Re: Visual Basic vs. PowerBuilder Date: 10 Dec 1994 04:45:55 GMT Organization: MCSNet Services Lines: 30 Message-ID: <3cbbq3$gcm@News1.mcs.com> References: <davebo.18.0010EDAE@mcs.com> <3c2lmn$669@explorer.csc.com> NNTP-Posting-Host: rayg.pr.mcs.net mpfeifer@csc.com (Mark Pfeifer) wrote: > > The simply answer is if you want to do database applications, > PowerBuilder is going to be a better choice. Visual Basic does > not offer any control which is > equivalent to PB's DataWindow. > > This control can save some signifcant coding time. > I have never worked with Powerbuilder, but I have ben building client server apps with VB since 1.0. From what I understand about Powerbuilder, I believe this to be an accurate statement: Visual Basic is a Windows programming language with data access features build in. Powerbuilder is a database front end builder for Windows. I do have a question about Powerbuilder. My VB applications are run on 95 Novell file servers by about 3000 users a month about 17000 times. How would Powerbuilder work out in this environment? I have heard that if more than 10 users try to run a Powerbuilder application it starts to slow down. Is that a correct "rumor"? Raymond Glassmeyer rayg@mcs.com