Hi, We have a client that decided some time ago to upgrade their executables to version 3.60. Since that time, they have decided to upgrade the entire database to 3.70. When I open their v2.0 (with 3.60 Exe) in version 3.70 I don’t get any of the messages saying things like, “do you wish to convert the database” etc etc. I can also then open the database in 3.60 again. Is it supposed to be OK to do this or am I just doing something wrong? [B)]
Hi, That’s because the database version is the same between 3.60 and 3.70. Navision doesn’t always update the database version on each release. They only do it when they want to include support for some new technology, like 1024 characters Text variables, DateTime data type or RecordRef/FieldRef/KeyRef, etc.
Thanks Nelson. A very helpful and speedy response! [8D]
I have got a situation where the 3.70 SQL client installation on my desktop PC prompts with the “do you wish to convert the database” message when I try to open a newly restored 2.6 SQL database (restored into a db created with 3.7 client) but the 3.7 SQL client installation on the server machine does not. Also, if I do go ahead and convert the database with my desktop 3.7 client I then can’t open it again with the 3.7 client on the server machine. It says something like… “can’t open the database because it has been opened with a newer version of the program”. I have double checked the finsql.exe versions on both machines and they are exactly the same (3.70.0.14555). The server machine does also have an installation of Navision 2.6 but then so does my desktop machine. Does anybody have any ideas why the same versions of the client program are behaving differently according to where ther are installed?
Thats pretty strange. I don’t know if it helps but i didn’t think you needed to backup and then restore in 2.6 or higher, you can just open them. This is normally the point at which you get a “do you wish to convert…” message. Once you click yes the program handles everything automatically (or at least i thought it did). This is certainly the case with native DB’s but not sure where this stands in relation to SQL… sorry! I hope this helps and i haven’t misundestood your posting, but i will be the first to admit my knowledge of SQL is pretty much 0.
Check the version stamps of ndbcs.dll on each machine. It is this dll that deals with 90% of the SQL implementation - and it is here that these version checks and conversions are handled. The questions is, why is one of the machines running with a mis-matched version to finsql.exe? It must be version 3.70.0.14988 I would guess. (As a side-question, why have you installed Navision on the server machine?)