Re: Visual Basic 4 as a front end to Informix on Client-Server

In article <45rdaj$bq9@oslo-nntp.eunet.no> olavt@ksedb.no (Olav Tollefsen) writes: >In article <813766639.20840@mlachlan.demon.co.uk> >roger@mlachlan.demon.co.uk (Roger McLachlan) wrote: > >> 1. Should we be using ODBC to get from the client to the server (is >> there any other choice?). I've heard dire things about the performance >> implications. > >MS SQL Server 6.0 has achieved *very* good TPC-C benchmark results using >the ODBC on the clients. > How nice. Did you note that Roger specifically said he *didn't* want to change the server engine? >> 3. With VB being an interpreted rather than a compiled language, is >> there any scope for re-using code between modules? If not what happens >> about source control? I am worried about writing the same bit of code >> 50 times for 50 different programs, then finding a bug and having to >> correct it in 50 places. Is there any scope for 'library' functions? > >You can compile VB code into a .EXE with VB 4.0. You can also use Visual Source >Safe for version control. > >-- >- Olav Tollefsen >- Microsoft Norway >- You have a lot of other options. Viewpoint Pro and NewEra from Informix and Delphi from Borland are the ones I have played around with (in the sense that I haven't deployed production apps yet). These work; how well depends on what your app needs to do. Informix claims the ODBC speed penalty using their drivers to their servers is around 3%. IMO, not enough to worry about. Peter Wiley