Visual Basic/SQL-Retriever/Informix Limitations
Posted in 1994
Topics: Stored Procedures & SPL, Connectivity: ESQL/C, 4GL & Embedded SQL, Triggers, Constraints & Referential Integrity
Hi everybody. My group is about to develop many client/server applications, whereby the clients will be PCs and the server is an HP Apollo 9000 Series 710 UNIX workstation. We're currently running Informix Online 5.01 and I-Star and the server code is written in C using I-ESQL with some usage of triggers and stored procedures. We've been investigating front-end packages, namely Informix Hyperscript, but for various reasons, we would prefer to use a more established GUI package like Visual Basic. SQL-Retriever appears to be a great product, especially the feature of being able to detect if any database table change has occurred within a specified time interval. Are there any Informix limitations using a Visual Basic & SQL-Retriever setup? Can you still perform ALL of the Informix SQL type statements, in particular, selecting records one by one using a cursor. From my brief readings, it appears you can't use SQL statements like prepare/declare/ open/fetch, but instead you can select everything into an array on the client and then manipulate the array row by row. Before deciding 100% to use SQL-Retriever, I need to know if all of the SQL type features can be used and/or at least something that is equivalent to the SQL command. Also, are there any other limitations dealing with anything else, especially when running SQL-Retriever over a serial line? Any help would be appreciated. thanks. byron@nyh4.ebi.com