At 03:43 PM 2/2/2010, Roberts, Jennifer wrote:
I am receiving I/O errors in an area of my database where Im using temp tables. I have one form that is using two temp tables and I have changed the code to create the temp tables before calling the form. However Im still getting the I/O errors.
That is a typical symptom of invalid SCRATCH settings and/or mismatched R:BASE Engine files in path. Using the Windows file search option, check your entire computer for RBENGINE*.DLL file and compare the the new versus old. You may also need to verify the version and DLLs being used in your development environment versus the compiled application being used on your network server. File search option should reveal the result of found DLLs. SHOW SCRATCH at the R> prompt will return your current SCRATCH settings.
I receive the I/O errors on the drop table lines.
Make sure that the table is not opened in database explorer or that form associated with the table is not being worked on in form designer. If any CURSOR was DECLARED against this table, make sure to DROP the cursor before using the DROP table command.
After the temp tables are created I can go into the database explorer and open the temp tables without any problem, but if I try to design on the table I receive the I/O errors check for full disc then database files are out of sync . then a message stating that the table has been changed, do I want to save changes. If I click on yes here it states that there are no columns defined and I can see that there is no table name either.
When opening a table in Data Designer, a mirror copy of the table along with current structure and data gets stored in a temporary zone (R:Zone). Again, you have to make sure that your R:BASE SCRATCH settings are defined correctly and you are not using the latest RBG executable with old R:BASE Engine files. Hardware issues, such as bad memory chips, or bad sectors on your hard drive may also result in such symptoms. When was the last time you checked the "Health" of your database? When was the last time you re-built the entire database using UNLOAD/LOAD option to check the integrity of your database and system tables? That should provide you with some Blue's Clues ... Very Best R:egards, Razzak.
