Re: MS-ACCESS as a client front-end?

lou2@cbnews.cb.att.com (louis.avrami..jr) wrote: >Hello, > My group is just beginning to venture into the client/server >area. One of the server databases that we need to access is INFORMIX >ONLINE 5.02, running on an AT&T (NCR) 3555 using the UNIX System V >Release 4 (SVR4) operating system. > Much of the PC/Windows development that has been done here in >the past has utilized MS-ACCESS 2.0. > My questions are: can MS-ACCESS serve as a proper client to the >UNIX/INFORMIX database server? Does MS-ACCESS properly partition the >components of client/server applications? > Another factor to consider is that some clients will have local >LAN connections, some WAN connections, and a few will require SLIP/PPP >(telecommuters). > Any advice, warnings, information, etc. will be greatly appreciated. >Thanks, >Lou Avrami ( attmail!lavrami ) >AT&T Law & Government Affairs I would not recommend MS Access as a front end for REAL client server development. It's OK for stand alone PC apps. If you want to leverage your in house skills, you might want to look at Visual Basic. It uses the same (Basic) language as Access, but is a little more robust. It's not really appropriate for large scale (enterprise) development, so keep that in mind. If you want to avoid C++, but need a scalable 4GL type tool, you need to look at things like Forte. Stay away from Powerbuilder, it's all hype. If you do go with Visual Basic, do not (repeat NOT) use bound data controls - they will get you into far more trouble than they are worth. Paul. "Nothing in this post is necessarily the opinion of anyone living or dead, and any similarities thereto are strictly intentional"