I don’t think the error comes up when you programmatically create or alter a table. Just when you are using the data explorer or typing from the r>
As with all updates from anybody, I always test it first before using it in production. Dan Goldberg From: Jim Belisle Sent: Thursday, September 15, 2011 12:00 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: New update problem I have not implemented the latest update for 7.6 since I am out of the country. The thread from Dan about the ERROR message makes me wonder if I may run into problems if I implement the Update. I have code that I use to create a new table on the fly, allows me to edit it, imports the new info into a master table, then deletes the created table. Is this new enhancement going to create problems for me? I do not change any existing table structures, just create new tables and then deletes them. Plus I use temp tables throughout the application. James Belisle -------------------------------------------------------------------------------- From: [email protected] [mailto:[email protected]] On Behalf Of Dan Goldberg Sent: Thursday, September 15, 2011 11:37 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: New update problem I think it is a good enhancement but for us veterans we know what we can do or not. Also, it also comes up when we are working on temporary tables as well. Which does not affect other users. Dan Goldberg From: A. Razzak Memon Sent: Thursday, September 15, 2011 9:24 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: New update problem At 11:25 AM 9/15/2011, Dan Goldberg wrote: >Using today's update I keep getting the error message: >Warning – There are other users connected to the database, Structural >changes should be performed in single user mode to avoid database >corruption. >Is there a way to turn this off? Dan, This eXclusive enhancement is implemented to give users and database administrators a -Warning- when mucking with tables using the Data designer, while in a multi-user environment. Would you rather get a -Warning-, or screw up the table and database, creating ghost tables, and not realizing the fact that there are other users using the same database? This submitted enhancement request was implemented to avoid such issues when working in a multi-user environment. Very Best R:egards, Razzak.
