Re: client/server ms windows 3.1 applications development

In <1993Jul1.174824.13907_at_cs.rit.edu> mdp8018_at_cs.rit.edu (Mark D Pollard) writes:

>I am looking for any comments, warnings, or suggestions regarding the following:

Some random comments:
>(2) Should we (do we need) a Novell TCP/IP product to access the Oracle
> data from the laptops? If there are other, better Novell compatible
> TCP/IP products, please let me know.
Yes, you need a TCP/IP. There are two other products that come to mind, FTP S/W's PCTCP and NetManage's Chameleon. I've tested both of these products, although not with SQL*Net. There is no perfect solution to the TCP under Windows problem. You are always trading stability for speed for conventional memory. Email me if you want more info on this subject.
>(3) Once the data has been transferred to a laptop based product (Microsoft
> Access would seem to be ideal given its bundling with MS Office) is Access
> a solid development product - or should the step up to Visual Basic be
> t
Access is fine for ad-hoc work, but I don't feel that it is a good vehicle for turn-key applications for end users. VB is much better, but doesn't have reporting or ad-hoc capability built in, you must build it yourself.

>(4) Is Visual Basic appropriate? What about other products like PowerBuilder?
> Understand, a localized (laptop) DB is needed when the laptops are pulled
> off the ethernet and taken home.
Powerbuilder does not have it's own database, if you need a SQL database on the laptop, look at Watcom and Gupta. I don't beleive that the ORACLE PC standalone will work in a Windows environment (I may be wrong on this)

>Thank you for your time. Please feel free to point out any important
>considerations I have missed.
 

>Mark Pollard
>mdp8018_at_cs.rit.edu

Dave

-- 
David Benua                  Internet: dbenua_at_panix.com 
	                   Compu$erve: 72630,1416