what problems did you run into using create temp ? ----- Original Message ----- From: Roberts, Jennifer To: RBASE-L Mailing List Sent: Friday, February 05, 2010 8:10 AM Subject: [RBASE-L] - Re: I/O error redux
Hello, I used to use the 'create temp' to create these temp tables but it seemed to have had more problems than using the 'project'. I have checked for any old versions of rbengine cfg files and dll files and have verified that I have the same files in my development environment. I have double and triple checked my files where I am developing and compiling the application (my computer) and the files that are residing with the executable on the server. I have checked the server and all the network drives for any old cfg or dll files and removed and/or renamed all of them. I have recompiled the executable. I have also unloaded/reloaded the database and ran the database integrity routine and I am unable to get any errors. The users are using remote desktop to log into the server and then run the compiled application. I know that these users have old dll and cfg files on their computers. I would not think that this would cause an issue since they are using the remote desktop, but could it? I am going to get with all of them over the next few days and remove all of their old files and see if this helps. Thank you to all who have given me suggestions. Jennifer From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, February 02, 2010 6:05 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: I/O error redux I'm not sure I've ever done a 'project temp'; I always do a 'create temp'. Project temp is certainly easier, and it should behave, but I agree with Rachel -- try replacing it with a create / insert and see if that takes care of it. Karen I've run into issue where any of the fields projected are computed. I also do all temp table creation BEFORE calling the form and if you still run into issues don't do a project but a 'create temp table...' syntax. GOOD LUCK! 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.
