I would disconnect all users before making any design changes.
Make schema change when a user has lock will always produce the "error" message.
I dont think you can find any RDBMS that will allow this.
Allowing this would wreak havoc with data integrity among other things.
Yes, users can be in the system, but as Rick says, it's best to not do that. And as Kris says, the users cannot have records open in the tables you're modifying. This is a feature, not a bug.
You can, but you shouldn't. And if the error message comes up, hit cancel at the speed of light.
Thanks for the information. I have been using FM for around 10 years and it has been something I wondered about so I thought I would ask the question.
As you say I normally don't or if I get the error message press cancel and get everyone off the table I am trying to update.
Thanks for the information.
Further expanding on what's been said already, making schema changes to a live database is very risky. I once completely corrupted a database doing this (before I realized it was a Very Bad Idea). It's generally best to make your changes on an offline copy (or on a development server) and move the changed code up to the production area when you're satisfied it's working properly.
BTW - This also gives you a chance to test the changes prior to moving them to production. You often prevent Bad Things from happening if you test changes first.
Thank you. All makes perfect sense.
Sent from my iPhone
Sometimes Mike's advice is not possible. I always backup, BackUp, BACKUP (via server schedule) the entire solution just before these kinds of changes. And if possible work "after hours" to limit the number of users.