Fundamentals of "old" Navision

Nav123: Navision, Showare, OrderApp

Print Friendly, PDF & Email

Your Navision is not old... and that is completely independent of the version number. Of course, each new version also gives them new capabilities along the way. To address a REST-Api with DOS-Navision 3.53 or 3.56 is a bit of a pain... but possible! Just like sending PDF's via email. Have a look at my page!

Follow this link for old versions & Setup-DVD's

Introduction


For me, the highlight was

*Usability
*Speed of operation
*Simplicity of adjustment
*Functionality of the application

given with the native 2009R2 solution - not with the 2009R RTC, which was the usual Microsoft mess... continued with Navision / Business Central 2013. From 2013 r2 it then became properly usable again for the first time.

But detached from that: article stocks, G/L account balances, debit & credit and special prices do not change, not even in 30 years. And the rest around it, like webshop, end customer app, paperless picking, a PIM system, emails and all that stuff: We can teach that to your Navision, too, if you want. This way, your Navision, which you paid for long ago and which -if your maintenance contract is cancelled- can be used permanently free of charge, continues to be the driving force in the basement of your company's IT.

Für den RTC ist für mich Navision 2018/BC14 das Optimum, da auch hier nahezu alle Kinderkrankheiten des RTC’s abgestellt waren und das System endlich produktiv eingesetzt werden konnte. Was man von Navision 2013, 2015 etc. nicht gerade sagen konnte. Navision 2017 war dann schon recht gut, und der neue Webclient von BC14/Navision 2018 ist dann auch der lang erwartete Befreiungsschlag gewesen.

But here, in this article, it should first be about the very basic things that you need from time to time, but which are increasingly difficult to find on the Internet. Please be patient, the page will be built up bit by bit. Feel free to contact me, wenn Sie fragen zu diesen Themen haben. Eine kurze Erst-Beratung ist im allgemeinen kostenlos.

I fill the corresponding part so little by little with content, if I just have to do with it. You just need a specific tutorial that is not yet available? Write me and I'll add it quickly.

Create a backup

Backup DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Backup Windows-Navision Financials, Dynamics (Business Central)

Anmerkung: Sie können mit ihrem nativen Navision auch vollautomatische Datensicherungen machen, dies passiert seit der 3er Version von Navision über das mitgelieferte Programm Hotcopy. Diese Datensicherungen (backups) sind aber immer eine 1:1 Kopie (Snapshop) ihrer laufenden Produktivdatenbank. Hier in diesem Abschnitt geht es um eine viel kompaktere Datensicherung (Backup), z.B. um sie zu einem Entwickler zu senden oder um daraus eine Testumgebung zu machen. Mit dieser Anleitung kann Ihre Datenbank für die Übermittlung leicht auf 1/10 der ursprünglichen Größe reduziert werden, und dann beim Empfänger typischerweise mit ca. 85% der originalen Größe wieder in Betrieb genommen werden.
Eine (z.B.) 40 Gb große Navision-Datenbank, gefüllt mit 35 Gb Daten(Datei/Datenbank/Information), kann auf dem hier beschriebenen Weg durchaus auf 3.5 Gb komprimiert werden. Diese Menge kann heutzutage problemlos über WeTransfer oder andere Wege übertragen werden kann.
Mit einem Scripteditor wie ac’tive Aid (Autohotkey) kann dieser Prozess auch automatisiert werden. Für ein reguläres tägliches Backup empfehle ich jedoch Hotcopy. Hinweis: Hotcopy sichert, genauso wie der SQL Server, immer die komplette Datenbank, also in unserem Beispiel 40Gb. Das kann aber auch (z.B. für sofort lauffähige Testumgebungen) durchaus gewünscht sein!

Preparation:

If someone else, e.g. I as a developer, should work with the sent database, it is important that he is also registered in it as a user with super rights. You make sure this via Tools/Access rights/Database logins:

Screenshot von Navision 2009R2 zum überprüfen, ob ein Benutzer die richtigen Rechte hat.

If I am your maintainer, this user is already set up in your database. If not, please enter me (or the recipient of the test database) there, if not already there.
If you run Navision with the SQL Server (which is possible with Nav 2009R2 without any problems, if you make a few adjustments...), it can be that the passwords are empty here. This is then also so OK.


Note: Most certainly your recipient of this backup will read their database natively, at least that's how it always works for me. If your recipient needs a SQL backup, the procedure is more complex.

Create a backup:

Please call Extras/Create data backup

Aufruf der integrierten Datensicherung in einem Classic Client (Navision von Version 2 über 3, 3.60, 4, 2005, 2009 R2 etc)

You can't go wrong with the [X] Whole Database settings.
Alternatively, you can also back up only individual clients. Then make sure that in any case
[X] Data shared for all clients and
[X] Application objects
are selected.

For the file name, please make sure that your company name, the current date, and behind the date a -01 is written, e.g.
c:\temp\companyname 20230220-01.fbk

Navision will usually create more than one backup file, for this the last digit is incremented, if there is none, one is appended.

Input: fin.fbk+


Result:
Fin.fbk
Fin1.fbk
Fin2.fbk

Input: Name Datum

Result:
Müller 20230220.fbk
Müller 20230221.fbk
Müller 20230222.fbk

Input: Name Date Attachment.

Result:
Müller 20230220-01.fbk
Müller 20230220-02.fbk
Müller 20230220-03.fbk


Now you can sit back, Navision will now create the backups for you.
If you want to send the database / data backup: The resulting files you can still significantly pack (make smaller / compress) with Windows ZIP!

Beispiel für die Verkleinerung einer Navisiondatenbank als gepackte Datensicherung

It is realistic to collapse a database in this way to about 1/10th - more likely even smaller.
A logical backup in this way requires about 1/3 of the original database content. Unlike SQL_Server, no empty database contents and no secondary keys are backed up.
The resulting backup files can be compressed to about 1/6 of their original size with Windows ZIP. With 7Zip even 1/10 are possible! For me you are welcome to use 7Zip, for other recipients clarify the packing program in advance. So even 70Gb databases can end up as a handy 5 Gb 7z packed backup e.g. burned to a DVD or sent via a service provider.

Advantage of e.g. 7Zip : You can not only pack the backup, but also provide it with a password at the same time. This password is best transmitted via a 2nd channel, e.g. instead of email with WhatsApp.
Advantage of Windows ZIP: This is already installed on all Windows computers and is only a mouse click away.

Sending a data backup, e.g. as a test database

If you want to send your database via a cloud service provider (as described below)'it is best to use the option to password protect the files when packing them.

Google Drive & OneDrive

Depending on how they are integrated, upload the created and packed backup files to your Onedrive or GoogleDrive folder, and create a share link from there. If you already use these services, they are usually the first choice, since you have between 15Gb of storage (Google) and 1Tb (OneDrive) available.

Dropbox

Free here is only 2Gb, reserved storage. This is very impractical, only recommended if you have a Dropbox account with more storage.

pCloud Transfer

To use without registration, already free of charge 5 Gb are possible, that is usually enough for databases with an original size of 50 Gb. The service can be called multiple times, so that even larger backups can be sent in these 5Gb chunks.
https://transfer.pcloud.com/

You simply drag the packed backups into the browser window with the mouse. You can also assign a password here via "Encrypt your Files".
Please enable "Get a Link to share" if you want to receive and share the link yourself, or enable Transfer via email if you want pCloud to send a mail directly to the recipient with the download link. If you need to transfer more than 5Gb, first drag the files up to this limit into the window, send the message, and then call the service again.

WeTransfer

The operation is similar to pCloud, also the workaround if you want to transfer more than 2Gb.

WeTransfer.com

With WeTransfer you still have to verify their sender address by a confirmation email, you can bypass this by registering once and for free.

Importing a data backup

Readback DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Reading back Windows-Navision Financials, Dynamics (Business Central)

Attention! The process for SQL database backup can be completely different! That is if you use the SQL_backup, which is legitimate. However, if you use Navision up to version 2009R2, you can actually still backup and restore an SQL_Database via the client, the process is then quite similar to the one described here. However, I will only discuss the native database (Classic Database Server) here, as this should be the main application for readers of this article.
You will also probably need this topic if you want to create a Navision test environment with the Classic Client. This is also possible if you simply copy the original database files, e.g. with HOTCOPY, and then open them with the client... however, these files become quite unhandy if you want to send them.

Let's Go!

With the 2009 (or 2.01, 3.70 etc.) client you create an empty fresh database. This should not be more than 30Gb in size, otherwise it will later result in the error message
"The operating system has issued the error message (665): The requested operation could not be completed due to a file system limitation."
I haven't been able to pinpoint an exact limit yet, but from my own experience I just try to stay under 32Gb, so 30Gb is an easy limit to remember.
Really stupid: You may be able to access the database a few times, and then get this error message sometime later. If you have the Navision database on a compressed or encrypted drive, try moving it to a normal drive and see if you can access it again. This is not safe. You may also have to restore the database again, according to these instructions.

Mögliche Fehlermeldung bei Navision mit einer zu großen Datenbankdatei: Das Betriebsystem hat die Fehlmeldung (665) ausgegeben: Der angeforderte Vorgang konnte aufgrund einer Dateisystemeinschränkung nicht abgeschlossen werden.

Start the client, go to File/Database/New:

If you have a target size for the database up to/below 30 Gb (30,000,000 Kb), specify the database size in Kb directly in the following dialog:

If you have a target database size over 30 Gb (30,000,000 Kb), specify only a small database size (hull size) in the following dialog:

Determine the approximate database size needed: you will need about three times the file sizes of the backup:

Anzeige der Größe einer Datensicherung aus dem Classic Client Navision Dynamics Attain 2009R2

Please note the uncompressed size here. Both data backups and a test database can be stored wonderfully on a Windows-compressed and/or Bitlocker-encrypted hard disk partition / directory in the native (Classic Client) Navision.

Rule of thumb: Backup size x 3, so here approx. 34 Gb x 3 = 102 Gb. Clearly more than the recommended 30/32 Gb.

Extending a multi-part database: If, as in this example, you already know that the database will be more than the infamous 30 Gb, you have, after all, only created a trunk database to begin with.

You can expand this (or any other multi-part database) here:

Erweitern einer Mehrteiligen Datenbank unter Navision Financials bis 2009R2

Please also note this information (also below under Extend): Only one database part may be created per physical hard disk. This is especially important for SAN/NAS with Raid5 hard disks! If more than one database part touches a physical hard disk, the write/read optimizations per database part will get in each other's way. Of course, this is not so crucial for a test database.

Tip: Copy down the values with the F8 key (works everywhere in the Classic Client!) and adjust only the details.
Then OK, and sit back and wait.

Fortschrittsbalken beim Vergrößern einer Mehrteiligen Datenbank unter Navision Dynamics Classic Client mit einer nativen Datenbank

The progress indicator applies per individual database part, it therefore appears in this example 4 x for the 4 database parts.

Now it is time to import the backup. Make sure that the backup files are numbered consecutively. Sometimes they are also numbered according to the pattern
fin.fbk
fin2.fbk
fin3.fbk, in that case someone has not read my instructions here.

Then rename fin.fbk to fin1.fbk before the next step.

Einlesen einer nativen Datensicherung von FBK Dateien in eine Classic Client Datenbank


Navision Financials/Dynamics then asks again what it should read in from this backup:

And then it starts with the readback. SSD is quite fast, HDD takes forever.
Attention. After the pure data has been read in from the backup files, all secondary keys must still be created, Navision does this automatically.

If the previously created database is too small for data import, you need to expand the Navision Dynamics database in the known way, and import it again.

If the previously created database is too small for the keys, you have to extend the Navision Dynamics database in the known way, and call the Import Database function. Navision will then continue the key creation at the aborted location.

Statusanzeige von Navision Financials mit dem nativen Client (z.B. bis Version 2009R2) beim Rücklesen einer Datensicherung.

At the end, Navision once again reports that the backup has been successfully imported, and that's it.


In my experience there is only one situation in which Navision Dynamics does NOT read in its data backup, and that concerns errors in tables, i.e. table objects which cannot be compiled. But you don't do something like that.

Attention! Directly after the backup was read in one go (not if the database had to be extended in between), there is an interesting point! ( The one immediately after The backup has been read successfully):
You can now create users or assign rights - even or especially because you have not yet had to log in to the database! Depending on the version, you can also set/delete passwords here. This can be an "emergency nail"!
And one more hint: If you read a backup created by Navision Dynamics/Financials under SQL with the native client back into a native Navision database, all passwords assigned under the SQL Server are NOT included in Navision! You must then either immediately create a valid (super) user, set a password for a user, or log in later with the username WITHOUT password or with the password from BEFORE the SQL Server conversion (if the user already existed then)!

Installieren/Einrichten eines Clients

Installieren/Einrichten Navision 3.53,3.56

Kopieren Sie einfach den gesamten Ordner eines laufenden Clients auf einen neuen Computer. I.d.R. starten Sie dann dort die navin.exe, oder haben bereits eine Batchdatei sowie eine LNK Datei für den Start. Ein „Setup“ im eigentlichen Sinne brauchen Sie hier nicht. Sie können es aber von den 2 original Disketten starten.
Als kleiner Hintergrund:
navi.exe: Die normale DOS Executable
navin.exe: Navision für Nt (daher das N in naviN.exe). Dieses Navision kann bis zu 2 Mb (glaube ich) RAM verwenden, ein riesen Fortschritt gegenüber dem klassischen Client. Dieser wird aber nicht für Daten benutzt, sonder für verschachtelte Funktionsaufrufe.

Installieren/Einrichten Navision 2.01, 2.60, 3.01, 3.60

Installieren/Einrichten Navision ab ca. 4.0

richten Sie auf aktuellen Windows-Clients zuerst .Net 3.5x ein:

Dann starten Sie das C/Side Client Setup:

Akzeptieren Sie die Lizenzbedingungen, geben Sie einen Usernamen ein, wählen Sie dann bitte „Custom“ aus:

Wählen Sie dann bitte diese Optionen:

Next, dann „Install“.

Die Installation wird nun durchgeführt.

Auf manchen Systemen, sowohl Windows 10 wie auch Windows 11, habe ich diese Setupdatei aber einfach nicht zum Laufen gebracht. In diesem Fall hilft dieser kleine Workarround:
Starten Sie das CSideClient Setup einfach direkt:
Sie finden in ihrem Ordner einen Ordner CsideClient, und darin eine Microsoft Dynamics NAV Classic.msi, welche Sie auch direkt aufrufen können. Sie landen dann in diesem Setup:

Klicken Sie sich kurz durch die ersten Einstellungen, Sie landen dann wieder bei dem weiter oben beschriebenen Setup.

Wenn alles gar nicht hilft: Sie können auch notfalls den Navision-Programm-Ordner von einem funktionierenden Client auf einen neuen Client kopieren, „Das meiste“ von Navision wird dann auch laufen. Alles was Navision-spezifische DotNet-Bibliotheken benötigt, funktioniert dann aber nicht. Sie können auch diese einzeln nachinstallieren, das übersteigt dann aber den Umfang dieser Anleitung. Wenn Sie hier Hilfe benötigen, kontaktieren Sie mich bitte.

Ab und zu vergisst das Navision setup das Umkopieren der angepassten fin.flf, und, noch ärgerlicher, der deutschen Sprachschicht.

Beides ist schnell korrigiert.
Kopieren Sie bitte ihre Firmen FIN.FLF Datei in den neuen Programmordner.
Zusätzlich prüfen Sie dort bitte, ob der DEU Ordner existiert. Wenn dieser fehlt, können Sie ihr Navision nicht auf Deutsch umschalten.

Kopieren sie dann bitte aus ihrem Setupordner, z.B. Z:\NaviSetup\CsideClient\program files\Microsoft Dynamics NAV\60\Classic den Ordner DEU in ihren Navision-Programmordner:

Wenn dies nicht auf anhieb klappt, z.B. weil Windows beim „Einfügen“ meckert, das der Quellpfad nicht verfügbar ist, so hat der Explorer den Userkontext umgeschaltet. Das macht nix! Kopieren Sie die DEU Datei und evtl. auch die fin.flf zuerst auf z.B. c:\temp (wichtig ist, das es ein lokaler Ordner ist, kein Netzwerkordner), und dann kopieren Sie die Datei/den Ordner von c:\temp\ in den Programme Ordner, wie oben gezeigt.

Nach einem Neustart steht Ihnen dann „Deutsch“ als Anwendungssprache zur Verfügung.

Extra Tipp: Wenn Sie beides (die fin.flf und den DEU Ordner) VOR dem ersten Start überprüfen und ggf. nachholen, startet Ihr Navision sofort mit der deutschen Oberfläche, und Sie müssen nichts mehr umstellen.

Starting the client/application

Client DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Client Windows-Navision Financials, Dynamics

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Starting the database server

Server DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Server Windows-Navision Financials, Dynamics

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Aktualisieren einer Lizenzdatei

DOS-Navision 3.5x, 3.53, 3.56

Die Lizenzdatei hieß immer navi_inf.dat. Diese musste in jeden Clientorder kopiert werden, und in den Server-Ordner. Sie erhalten heute keine neuen Lizenzdateien mehr für das DOS Navision.

Windows-Navision Financials, Dynamics Classic Client

Kopieren Sie die Lizenzdatei in den Serverordner. Alternativ können Sie auch von jedem Client aus über Extras/Lizenzdatei/Import diese Lizenzdatei an den Server übertragen. Die erste Lizenz sollten Sie auch in jeden Navision-Clientorder kopieren. Navision fragt hieraus aber nur ab, ob es sich mit einem Server verbinden darf, und holt sich dann nach dem Verbinden die gültige Lizenzdatei vom Server. Nach dem Importieren der neuen Lizenzdatei müssen Sie den Client erst neu starten, damit er die neue Lizenzdatei vom Server holt.

Aktualisieren/Importieren einer neuen Navision Lizenzdatei fin.flf

Übrigens: Über „Export“ können Sie lediglich die lokale Lizenzdatei exportieren, nicht die Servergespeicherte.

SQL-option bis zu Navision 2018

Starten Sie den (Entwicklungs-)Client, und rufen Sie die Lizenzanzeige über Extras/Lizenzinformation auf. Wie beim letzten Punkt, aber der Menübutton heist „Upload“.
Übrigens: Über „Export“ können Sie lediglich die lokale Lizenzdatei exportieren, nicht die Servergespeicherte. Nach dem Upload der neuen Lizenzdatei müssen Sie den Client erst neu starten, damit er die neue Lizenzdatei vom Server holt.

Einrichten eines 2. Navision Datenbankservers

Server DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Server Windows-Navision Financials, Dynamics

Diese Anleitung geht davon aus, das bereits ein Nativer (Classic Client) Navision Datenbankserver installiert und betriebsbereit ist, siehe vorherige Anleitung.

Suchen Sie das Programmverzeichnis des bisherigen Navision-Datenbankservers und kopieren Sie es, z. B:

Wenn Sie dem neuen Ordner einen aussagekräftigen Namen verpassen wollen („Mein Test-DB-Server“), dann ist dies der richtige Zeitpunkt. Notieren Sie sich den neuen Ordnernamen.

Suchen Sie sich aus den Diensten den Dienstenamen des bisherigen Servers heraus:

In diesem Screenshot ist dies SERVER1

Tragen Sie den alten UND den neuen Server in der HOSTS und SERVICES ein (Ja, die gibt es immer noch…)

Die Navision Clients und Server holen sich, wenn sie keinen passenden Eintrag in der Services und in der Hosts finden, den Port 2407 aus dem Navi-Programm selber, diese Vorgabe ist nicht änderbar.

Die passenden Einträge müssen auf JEDEM Client vorgenommen werden. Hier gilt der Parameter servername= für die Auflösung nach Hosts/Services. Normalerweise sorgt der DNS für die Zuteilung der richtigen IP Adresse. Wenn wir aber den Port vorgeben wollen (und das müssen wir, wenn wir mehrere Server gleichzeitig betreiben wollen), kommen wir nicht um das editieren der SERVICES und HOSTS drum herum. Navision schaut immer zuerst in der HOSTS, ob es dort einen passenden Eintrag für den Servernamen findet, wenn ja, schaut es noch mal in der Services nach dem passenden Port. Wenn der Servername in der Hosts fehlt, wird auch kein Versuch in der Services vorgenommen, in diesem Fall wird der Server via DNS gesucht und ein Verbindungsversuch findet auf dem Standardport 2407 statt.

Hier erst mal der Link zu einer anderen anleitung, bis ich das hier „in schön“ fertig machen kann.
Achtung! Diese Verlinkte Anleitung How To install multiple DB-servers on 1 PC (for development)? | mibuso.com wird eine normale Installation unbrauchbar machen! Die ist eher für Entwickler geeignet.

Setting up the NAS Navision Application Server Parameters

The initial setup of a NAS from Navision 3.01 to 2009R2 does not know a graphical interface. It is completely configured on the command line - and that very easily and quickly. After that, the running NAS can be configured graphically as a SnapIn in the management console. "In principle" this also works with an unconfigured NAS, but that almost always jams.

Before configuring, you should think about...

  • Which user should this NAS use. Often a network and Navision superuser is used. This is the most convenient solution, but it is not the most secure.
  • Which parameter should the NAS pass to the function with ID 99 (usually NASHandlerbut the name is not important. Decisive is the ID 99!) in the code unit 1? For the original JobQueue this could be JOBQUEUE (as I generally recommend).
  • Which database server, which instance, which client should be used by this NAS?

After these things are cleared up, we are ready to go. The NAS can simply be copied from its source on the DVD to its destination folder, e.g. C:\Program Files (x86)\Microsoft Dynamics NAV\60\Application ServerThe setup program essentially does nothing more than query the following parameters, copy the NAS, and start it with the queried parameters.

I recommend the following procedure:
Start the NAS locally with the correct parameters. This usually takes a few tries until they are correct. As soon as it is running, it is registered as a service with InstallAsService.

Parameters that the NAS.exe or NASsql.exe understands, separated by commas:

  • appservername The name of the Navision service in the service control. With net start appservername the service can be started from the command line, and accordingly stopped again with net stop appservername (if it was installed as a service).
  • nettype The network protocol to be used, usually TCP or TCPS. *
  • servername Name of the server (both native and SQL! But of course the used NAS must match the server, so nas.exe for the native database server and nassql.exe for the SQL server. For sql-server the instance is appended directly to the server name, e.g. NavSqlServer\Instanz3*
  • database is only used with SQL Server. With the native database server the server already knows the database. Exception: If the NAS is to process a native database completely autonomously, e.g. every morning a database backed up with hotcopy is to be switched to test mode. *
  • company Name of the client to be used. The NAS in the Classic versions can only handle one client at a time! It is recommended to put the client in "", i.e. company=“My Client*
  • startupparameter Which text should be transferred to the function with ID 99 in code unit 1.
  • objectcache Program code memory size. 32000 is usually OK.
  • installasservice installs the parameterized NAS as a service.
  • uninstallasservice uninstalls the parameterized NAS as a service. No program files are deleted in the process! It may be necessary to specify the desired service with the appservername parameter.

The parameters with a * can be queried in any running Navision client via File/Database/Information, and the current client is displayed in the title bar for this purpose.

Here no user was (and can!) be provided! The user must be entered after the installation as a service in the service console for the corresponding NAS service, and then this must be restarted.

*

Output of programs / objects

Output DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Output Windows-Navision Financials, Dynamics

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Reading in programs / objects

Read DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Einlesen von Objekten in Windows-Navision Financials, Dynamics

Wenn Sie ihre Programmänderungen („Objekt“ oder „Objekte“) z.B. von mir oder einem anderen Navisionpartner per Mail erhalten haben:
Speichern Sie die einzulesenden Objekte in einem Ordner ab, auf den Sie schreibenden und lesenden Zugriff haben.

Then start Navision with a user that includes the group Super. These users often have a name like Super or Admin. In vielen Firmen haben aber auch der Geschäftsführer oder sogar alle Mitarbeiter diese Super-Zugriffsrechte. Hier finden Sie eine Erklärung, warum das nicht gut ist.

Start the development environment with Shift+F12:

Aufruf der integrierten Entwicklungsumgebung in den Windows-legacy Versionen von Navision
Starting the integrated development environment in the older Navision Windows versions

Der Objektdesigner startet, wenn Sie die nötigen Zugriffsrechte haben. Ihre Lizenz erlaubt das always allows this.

Ansicht des eingebauten Objektdesigners in Navision
Display of the integrated object designer in Navision

Call the import via the now changed file menu to start the import of the objects:

Importmenü aus Navision 2009 R2 und älter
The objects import menu from the old 2009 and similar Navision

Es startet der normale Windows-Datei Öffnen Dialog. Der Dateityp ist i.d.R. bereits auf den Dateityp FOB vorbelegt (Financials Gbject FIf you want or need to handle the file type TXT here, you don't need my instructions, then you are already a pro. Navision behaves differently with text objects! On the other hand, a look into such a text object is almost a look into the future: You practically already see what is nowadays called AL program code and is programmed at Business Central in Visual Studio here. You can transfer text objects from Navision 2.01 to AL with very few (also automatable!) adjustments!
Select the file with the Navision customizations ("Objects") to be read in and press "Open"

Angabe der FOB-Objektdatei zum  Import in Navision 2009R2, 2.01, 2.60, 3.01 etc.
Selection of a FOB object file for import into Navision 2009R2, 2.01, 2.60, 3.01 etc.

Als nächstes kommt eine Rückfrage, was Navision mit den gefundenen Objekten tun soll. Hier gibt es 2 verschiedene mögliche Dialoge, beide wollen von Ihnen wissen, ob Sie das Import Worksheet öffnen möchten. JA Ja ja, das möchten Sie, glauben Sie mir!
This one where you press OK:

Feedback from Navision in case of conflicts

Or this one, where you press No .

Rückfrage von Navision beim Import von einem Objekt oder mehreren Objekten zum Starten des Import-Worksheets

Es ist wichtig, dass in jedem Fall der folgende Dialog (Import Worksheet) geöffnet wird:

Import worksheet der älteren Navision-versionen bis Navision / Business Central 2018
Import worksheet from Navision. In any case, first press "Replace All" here.

Vergessen Sie hier an dieser Stelle auf keinen Fall, das „Replace all“ zu drücken, sonst führt Navision ein „Merge“ durch, siehe die obere Zeile. Das wollen Sie nicht, das will ich nicht, dass will ihr Nachbar nicht, und das will die Bundesregierung nicht. Glauben Sie mir. Niemand will das.
If this does slip through, please repeat the import immediately and remember to "Replace All".

After that, press "OK" in the Import Worksheet, then Navision / Business Central imports the programs ("objects") contained in the file, then displays a statistic, and that's it, done.

Users may still need to log out of Navision and log back in to take advantage of the changes. This may also apply to application servers that perform tasks in the background ("scheduler").

Enlarge database

For both versions: zooming in is easy, zooming out is not possible. Well... Maybe: Perform a complete logical database backup (i.e. not via hotcopy) via the client, delete database files, create new databases smaller, import backup again. But this is rarely necessary, e.g. if you have cleaned up your database and deleted old, unnecessary data from it..

Enlarge database DOS-Navision 3.5x, 3.53, 3.56

This topic will be filled with content when the opportunity arises. If you currently have a concrete need for it contact me!

Enlarge database Windows-Navision Financials, Dynamics

The easiest way to see if a database increase is necessary is to click here:

File/Database/Information - information about their server connection, the size and load of their database...
Größe & Füllstand der Navision-Datenbank im Classic Client
First page database information: size & level of Navision database.
Serververbindung & gewähltes Protokoll. Mit dem Parameter nettype=TCP(S) voreinstellbar.
Second page Database information: Server connection & selected protocol. At the NAS and at the client this can be preset with the parameter nettype=TCP(S). The server determines which protocol is valid!
Aktive Verbindungen zur Datenbank. Übrigens können Sie hier eine Session mit F4 löschen
Third page: The active connections to the database. By the way, you can select a session here and delete it with F4: The client will be disconnected from the database! This works from Navision 4.03 or so. Just try it out.

Important here is the level of the native Navision database on the first page of the database information. This should be between 80% and 95% for larger Navision databases.
Below 80%: The hard disk arms must overwrite unnecessary empty space in the database (does not apply to SSD, of course). Above 95: Larger processing operations may run out of free space in the database ("Other activities have overwritten the free space in the database").

You expand the databases via File/Database/Expand:

Erweitern der nativen Navision Datenbank
Extend the native Navision-Classic client database

Tip: Go immediately one step further to Advanced.

Erweiterte Ansicht Datenbankerweiterung (native Navisiondatenbank)
Advanced view of the database extension for a native Navision database

You can extend an existing database file here, or create a new database file.

Please note that the drives and directories of the Navision database server are meant here! With the selection you cannot select these - in contrast to the SQL server - however on your local client, you must enter these "blindly".

Recommendation: Keep individual database files under 30/32 Gb. Problems have been observed with larger database files. See reading back data backup. If you want to install a backup of a 80Gb database locally on your laptop, this has of course no significance. In this case, the proof of the pudding is in the eating.

Attention! When you create a new database section, please note this:

  • Only one database part may be created per physical hard disk. This is especially important for SAN/NAS with Raid5 hard disks! If more than one database section touches a physical hard disk, the read/write optimizations per database section will get in each other's way.
  • You may then have to adapt your data backups, test environments, etc. to the new database part!

In general, you should restart your database server at some point after an extension. It (or the first client that connects afterwards) then creates a "FreeMap list", which significantly speeds up write database access to the new free space. But even without this, the new space is immediately available.

Please also pay attention to the field "Licensed size"! Perhaps your license has not yet been updated. Since about Navision 4.0, with the first really usable integration of the SQL Server, the paid database size was removed from the license and generally 64 Gb was given free. At that time you could still get -with justification- licenses with 128 Gb and -in a few exceptional cases- with the maximum size of 256 Gb. As far as I know, these are no longer issued today, you must then necessarily switch to the SQL server or perform a database cleanup . Do not take SQL conversion lightly, you need to make some changes in code unit 12 and 22, optimize your keys, and check your date fields for dates below January 1, 1753. Also, there should be no forbidden special characters (line breaks, as they can slip into your database when inserting data from Excel) in your database. In case of doubt, I can support you with my own routines, which make this change a little less painful.

Register Automation Servers

In the native Navision & Dynamics versions from version 3.01 (was there actually a 3.00?) upwards, a then revolutionary technology was built in: Automation Server. This was then (2002 or so) something like .net is today. It allowed Navision Dynamics unimagined new possibilities. Direct interaction with Word & Excel, offering real-time web server services like my Infocenter, reacting to incoming mails incl. forwarding or extraction of mail attachments... And, an eternally missed and with the timer element on a form only rudimentarily replaceable timer function!!
Where do these automation server functions actually come from, you will ask yourself at the latest when you can no longer compile an object because Navision reports: The selected type library could not be loaded.
And then? Then just install the automation server 🙂
Well, of course it's not that simple, you have to know which one first...
A very popular one here is Microsoft Office 32 Bit (Navision Dynamics is a 32Bit application, so Nav can only contact Office 32 Bit. But you can install Office 32Bit and Office 64Bit in parallel on your computer without any problems!).
But the automation servers brought along by Navision itself also tend to attract unpleasant attention... and that is if you have not installed Navision on a computer, but have simply copied it onto it. Why should you do that? Because then it runs better! Navision Dynamics from about version 4.03 (more precisely: from hotfix 69) actually runs without problems on Windows 10 & Windows 11.... But not every version can be installed there, the installer is much more sensitive!

How are Navision's own automation servers installed?
First of all, find out which one is necessary. By the way, Navision does not reveal this in the variable declaration as usual:

Variablenliste unter Navision Classic Client, hier die Version 2009R2, mit einem unbekannten Automationserver
Display of the variable list with an unknown automation server under Navision Classic Client, here version 2009R2

Now you can do as much with Unknown Automation Server.Unknown Class as without any info at all.

Here the description of the variables helps! In this example Timer.

With this info, go to the \CsideClient\Common\Microsoft Dynamics NAV\ folder on your setup DVD and see what's there.

Ein Beispiel für das Nachinstallieren eines Unknown Automation Server.Unknown Class:Timer
Timer as an example for the post-installation of an Unknown Automation Server.Unknown Class

In this folder you will find a ntimer.dll. They are always DLL's or OCX's.
Other examples are the MSMAPI.OCX and the Navision Mailhandler.dll.
Please copy this NTimer.dll into the folder c:\windows\SysWOW64 (System Windows over Windows 64 Bit, main directory name can be different %Windows%) - best for all computers running Windows & Navision.
Then start a command prompt with administrator privileges, and change to the c:\windows\SysWOW64 folder:

Nachregistrieren eines Unknown Navision Automation Servers über den Aufruf einer Eingabeaufforderung MIT ADMINISTRATORRECHTEN
Calling a prompt WITH ADMINISTRATOR RIGHTS to re-register an Unknown Navision Automation Server

Now enter here: regsvr32 dll-name, e.g. regsvr32 ntimer.dll

Screenshot vom Unknown Automation Server.Unknown Class gelöst unter Navision Dynamics.
That's it, now the Unknown Automation Server.Unknown Class is a well-known automation server under Navision Dynamics.

In the same object, it now looks like this, and the object can be successfully compiled/used.