what's the rest of your code? if you run it internally (meaning not RDped in) do you still get the error? RBP can be a bugger. do you have it set up to RDp into one server with the DB files on another server? also a question to everyone but if you set everyone who RDps into the server, scratch to c:/temp wouldn't that mean everyone is using the same temp directory and could that cause issues?
and just to let you know, I've done all the suggestions too (checking scratch settings=still set to c:/temp, looking for extra dlls and config=nothing extra found, added -a to short cut=no better results, unload/load db=no change), and after a ton of time over the past 2 years plus new equipment, 99% of time have no issues but at times users will get I/Os. Sometimes it happens once or more a day BUT then other days nothing with nothing done different one day vrs another. These errors are random and all over the place and I can not recreate them but I've watched them happen. They go to print a report and get I/Os or picking the records to insert or when opening a form or doing nothing and return to the app. Sometimes the I/Os just keep coming up and the user has to end task, other times one or two I/Os, then what ever they are doing works, or maybe it doesn't. When it doesn't, the user closes the form, returning them to the source form that has a button to print the same report (or reopen the form) and it may work. If not, they return to the main menu and click a 'RESET' button to clear all vars and disconnects / reconnects to the database. Return to what ever they were doing when they got the I/O and it may work . If not they close out completely, resign in, and it may work...or not and they have to sign in and out till eventually it will work....OR doesn't ever and a reload of database will fix it. (Guess how happy a user is after that process just to get thier work done?) (please note, the following is intended as no disrespect to the hard work of the RBTI team. I'm just letting everyone know they are not alone with these issues and what I've discovered and what my result have been...) This past 2 years I have ran into issues when back up is still running on the server, low end graphics card (and setting the workstation to performance mode has helped this issue), a user had a virus and it was emailing like crazy, a bad network card, a faulty switch, a cut cat5 cable, poor code, a bad index, a bad record, an auto number column that didn't increment to the next value that blocked users from entering a new record....and on and on. It has been a ghost hunt for me to find the source and still haven't fixed it entirely. Sadly I have spent a bunch of time (and my client has paid a bunch for this) hunting, testing, reworking code, adding work arounds, hired a top of line network company who re-worked everything, new equipment, and with better results but compared to the money invested, not enough and unfortunately the client has canceled the project and is going with an online canned app. Even still this app is going to run for the next year and I just want to get it to work so I can comfortably move on to do another RBase project on a windows network...as of yet I'm not quite there but I want this to work so badly!!! I will still say it's the best DB development tool I've ever used (and I've been doing DB development for 10+ years), the price is right, and the support is great...it's just these I/Os and Access Violations errors are killing me! SO if you find something new or if I do, I will keep you posted!! and GOOD LUCK with the hunt, I hope you fair better then I!! ~Rachael oh and this is a V8 compiled app vrs 21.30903 ran locally pointed to a DB on a server running on a windows domain network. I'm hoping to update to latest shortly but am hesitant since I unloaded/loaded the db, recompiled, and updated 25 workstations last Nov ( and double checked for extra 'stuff') and it resulted in major I/Os, lock ups, and access violation for everyone, so I reverted back to this version (again the same process of unload/load, recompile, and updating the 25 workstations again) and right now most everyone is okay with this version. ----- Original Message ----- From: Roberts, Jennifer To: RBASE-L Mailing List Sent: Wednesday, February 10, 2010 8:03 AM Subject: [RBASE-L] - FW: [RBASE-L] - Re: I/O error redux Sending this in again because it didn't go through the first time. I did add the -a to the shortcut but still having issues. Jennifer Roberts Business Applications Specialist Ext: 5788 From: Roberts, Jennifer Sent: Friday, February 05, 2010 10:14 AM To: [email protected] Subject: RE: [RBASE-L] - Re: I/O error redux Scratch settings are set to c:/temp. All users are off site users connecting using RDP. Here is my code: SET ERROR MESSAGE 2038 OFF DROP TABLE tselecttype PROJECT TEMPORARY tselecttype FROM referraltypes + USING referraltype,description WHERE LIMIT = 0 DROP TABLE tselectagency PROJECT TEMPORARY tselectagency FROM agency + USING agencykey,agency,city WHERE LIMIT = 0 SET ERROR MESSAGE 2038 ON Here are the table structures: SET QUOTES=NULL SET QUOTES=' SET DELIMIT=NULL SET DELIMIT=',' SET LINEEND=NULL SET LINEEND='^' SET SEMI=NULL SET SEMI=';' SET PLUS=NULL SET PLUS='+' SET SINGLE=NULL SET SINGLE='_' SET MANY=NULL SET MANY='%' SET IDQUOTES=NULL SET IDQUOTES='`' SET CURRENCY '$' PREF 2 B DISCONNECT SET STATICDB OFF SET ROWLOCKS ON SET FASTLOCK OFF CREATE SCHEMA AUTHOR MSS PUBLIC CREATE TABLE `ReferralTypes` + (`ReferralType` TEXT (15) , + `Description` TEXT (30) ) COMMENT ON TABLE `ReferralTypes` IS + 'Referral types' And -> SET QUOTES=NULL SET QUOTES=' SET DELIMIT=NULL SET DELIMIT=',' SET LINEEND=NULL SET LINEEND='^' SET SEMI=NULL SET SEMI=';' SET PLUS=NULL SET PLUS='+' SET SINGLE=NULL SET SINGLE='_' SET MANY=NULL SET MANY='%' SET IDQUOTES=NULL SET IDQUOTES='`' SET CURRENCY '$' PREF 2 B DISCONNECT SET STATICDB OFF SET ROWLOCKS ON SET FASTLOCK OFF CREATE SCHEMA AUTHOR MSS PUBLIC CREATE TABLE `Agency` CASCADE + (`AgencyKEY` INTEGER NOT NULL + ('Value for column AgencyKEY cannot be null') , + `LastUpdateBy` TEXT (20) , + `AGUpdateDate` DATETIME , + `CaseManager` TEXT (20) NOT NULL + ('Please select the coordinator.') , + `Agency` TEXT (60) NOT NULL + ('Please enter a name for this agency.') , + `Address` NOTE (2042) , + `City` TEXT (20) , + `State` TEXT (2) , + `County` TEXT (15) , + `Zipcode` TEXT (10) , + `Phone` TEXT (15) , + `Phone2` TEXT (15) , + `Extension` TEXT (8) , + `Fax` TEXT (15) , + `agencytype` TEXT (15) , + `contact` NOTE , + `Comments` NOTE (2042) , + `WebAddress` TEXT (50) , + `IncomeQualifiers` NOTE , + `GeographicCoverage` NOTE , + `ApplicationReq` NOTE , + `Qualifications` NOTE , + `Limitations` NOTE , + `FeeStructure` NOTE (2042) ) ALTER TABLE `Agency` ADD PRIMARY KEY + (`AgencyKEY` ) + ('Values for rows in Agency must be unique',+ 'Cannot delete - values exist in another table',+ 'Cannot update - values exist in another table') AUTONUM `AgencyKEY` IN `Agency` USING + 13633. 1. NONUM COMMENT ON TABLE `Agency` IS + 'Agencies offering assistance' Thank you, Jennifer From: [email protected] [mailto:[email protected]] On Behalf Of Rachael Malberg Sent: Friday, February 05, 2010 10:05 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: I/O error redux and double check your scratch settings, if you set it to c:/temp as recommended then everyone connected via RDP is using the same directory for temp data. Just curious are these all off site users? This electronic message contains information from the Ohio Masonic Home, its operating subsidaiaries or affiliates. The information may be confidential, privileged or otherwise protected from disclosure. The information is intended to be received solely by [email protected], for use as designated in the message. If you are not the designated recipient, you are instructed not to review, disclose, copy, distribute orotherwise use of this transmission or its contents. If you have received this transmission in error, please notify the Ohio Masonic Home immediately at [email protected]; in addition, please delete your record of transmission. Sending, receiving, downloading, displaying, printing material that is harassing, fraudulent, offensive, intimidating, defamatory, or otherwise unlawful or inappropriate is strictly prohibited by The Ohio Masonic Home.
