MAJOR issue here: We running a 3.60A database in SQL at a customer site. However, one of the IT guys had a 3.70 client installed on his computer. Guess what… the guy opened the database with it’s 3.70 client! For sure, he had one screen asking him if he really wanted to convert to 3.70, but he clicked… YES ! [xx(] BOUM! Database converted! [:(!] 100 angry users can no more access the database (3.70) with their 3.60 clients!!! All of that caused by a simple click! To solve the problem, we did a backup of the 3.70 database (fbk) and restored it in a new 3.60A database. It works, but I still have questions:
- Is there a better way to solve the problem we had?
- Do we have to expect any issue because of the conversion from 3.70 to 3.60?
- Is it possible to restrict the ability to convert the database for the users (system permissions? code?)
I found an old topic about this issue telling me that I could do the following (http://www.navision.net/forum/topic.asp?TOPIC_ID=4826):
UPDATE [$ndo$dbproperty] SET [databaseversionno] = 5However, I’d like to know if anyone else have other suggestions. Tx in advance,