Not sure about ODBC but the oleDB port on UniData is 31438. There are a number of UniData files that are used when you generate the schema like: privilege, sysusers, sysobjects, SQLColumns, SQLTables, __schema__map, __v__view, etc. It will also create a D_DV_filename file for each file that you create a view on.
You should probably load the VSG from the client CD as it has a graphical front-end for all of the api's that are used to create the schema's. We figured the best approach was to create a new account and define pointers to the data files with local dictionary items. We then cleaned up the dictionaries and used them to create the schema. It works pretty slick. We are currently developing a number of Crystal reports against the schema. They work quite well. Hth Colin Alfke Calgary, Alberta -----Original Message----- From: Chauhan, Savita [mailto:[EMAIL PROTECTED] Sent: Monday, August 30, 2004 3:00 PM To: [EMAIL PROTECTED] Subject: [U2][UD] - ODBC Hi, How does ODBC (from MS Windows) actually connect to the UniData on Unix (AIX)? Is there any port listening to the ODBC requests from clients or is it something completely different? I want to know the Unix side of it. What changes are made to what files to be able to access UniData from client PC (apart from making the Unidata database ODBC compliant: by running convert.sql). Thanks. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
