mibuso.com

Shell-Substitute "Oyster"
Substitute for Navision-internal "Shell"-Command.
Prevents warning messages in Navision 4.0

Register it, make a suiting variable (Oyster) and use it like:

cmd:='notepad.exe';
if Oyster.Oyster(cmd) then ...;

You have to used a text variable (cmd), passing constant text will raise an error.

http://www.mibuso.com/dlinfo.asp?FileID=492

Discuss this download here.

there's a discussion in

http://www.mibuso.com/forum/viewtopic.php?p=22170

showing a better way to prevent from warning messages by using the MS-Shell

Sorry for my Question - maybe I am a little bit stupid.

I have registered the oyster.ocx.

How do I have to define a Variable "OYSTER" ?

Thank you !

In the form "C/AL Globals" or "C/AL Locals" you add a new line variable with

Name = Oyster
Data Type = OCX
and in column SubType you pick "Oyster.OysterCtl" from the lookup list.

Thanks,

But I don't have the Data-Type OCX ?!
Is it avaiable at a Report or only at CodeUnits ?

OCX are available in all types of objects. it might be restricted by licence??

Many Thanks,

I Think this is the problem - so we have to spend more money !!

You need the granule 1750 Tools - C/OCX

Up to 3.70 I wrote shell('net time /set /yes'); to sync the clients time.

In 4.0 Sp1 the %PATH% will be ignored and the net.exe not found!!!

I have to change it to shell('C:\Winnt\system32\net.exe ',' /set /yes');

Assuming, windows ist alway installed in C:\winnt, what is not true.
So the environment variable %SystemRoot" has to be determined.

Because of the short flashing up of a black CMD-Window, we use a similar
OCX automation server, wich gives us the possibility to hide the window.

To avoid the problems, that could rise with not registered OCX's, we have
merged it in the Navision client installer MSI.

You can use

or also ENVIRON('SystemRoot')
For all evironment-variables, open a dosbox and enter 'SET' as command. You will see all environment-variables.

Thats true,

but your have to find and modify all your shell calls before going to 4.x.

Not necessary, the shell calls that are always the same, you don't need to change. You give permission to run it once, and next time he won't ask permission anymore ... until you use it on another computer or delete your zup. (Can't remember if it is saved in the zup or in the registry). So better change it anyway.

Finding them is not so difficult: export all objects as text and search for 'SHELL'.

What would be really great, to have a method to return stdout from the application.

If I understood correctly what you want:
In the DOS-command, put "c:\..\MyCommand.exe > c:\temp\MyFile.txt"
This to save the stdout of the DOS-application into a file.
Then open the file in Navision and read it.

I want to use oyster to convert a file to another before I continue in NF.

How can I set oyster that he waits for the command to be ready (like it is in WaitVar := SHELL('notepad.exe'); )?