You probably need to do some back-end tuning and visit this URL for useful tips: http://www.softmall.com/as400/cs/csinfo.html

---

None, it is absoulty perfect! ?What is the best way to prevent them? Code directly to the ODBC API, do not use DAO or MS Data Control. Do not use attached tables via ACCESS. These are loser methods. Check out my web page @ www.sqlthing.com to see my product that access the 400, imports, exports, data mining, guery optimization, etc. Free beta/restricted version is available for immediate download. Also, I have FREE class object for direct ODBC manipulation of the as 400. You can download it from the web page next week. (Finishing the documentation, adding a sample database and example programs that you can run immeditaly, etc.) Here is what i do to prevent problems. 1. Issue STRDBG from client via ODBC to turn on message logging. 2. Issue query from client, . 3. DSPJOBLOG of odbc qzdasoinit qserver subsystem job and look at optimizer messages to determine how to tweak query. 4. repeat until perfect! 5. copy query into client application code. Also, make liberal use of stored procedures. For example, we have a data entry app the validates a few things, updates or inserts a summary record and then inserts the main record the operator has been working on. The program took 1.5 seconds to do this via ODBC with extended dynamic turned on. (5 sql statements to execute, 3 fetch and 2 modify) We took the logic and wrote an ILE C program, call it as a stored procedure in the same activation group of the calling program. We can execute the procedure 17.8 times per second from a single client. That is FAST! > create a table in DB2 using ODBC what is exactly created? Only a > physical file or also a logical file? Create table creates a physical file. Create index creates logical. Adding ref integrity adds LF's to the database. Create view creates a LF.

---