Hi! I have to check for a registry key, I was using tiral of WinBatchm, but run out of time, so I made a small app that read the key, end return wheter 0 or 1 in a text file key.txt, then I import that file in fileMaker. The problem is that when I run the readKey.exe from FileMaker, it doesnt generate any text file, when I run it myself it works. Is there any trick to do when talking from FileMaker to .NET !?!?!?

BTW, I'm not sure I posted in the correct forum, feel free to move to the appropriate place, thank you!.

How do you call the exe?

I do this kind of thing all the time so it should work.

readKey.exe and I will have another one called clearKey.exe

I think what Wim means is, how are you launching the .exe files from within filemaker. (The send event script step, for example)

I call it with Send Message["readKey.exe","aevt","odoc"]

well.. it works fine now. I don't really know why though... in my .net script, I change the file created at "key.txt" to "c:key.txt" and it works just fine... anyone would habe an idea?

A better way is to use a full command line syntax in the Send message instead of using the "open" in Send Message.

A command line like:

cmd /c c:someFolderyourExe.exe

Benefits:

- you can calculate this string to put in any location

- you can pass command line parameters to the exe

- much easier to troubleshoot by using "/k" instead of "/c"

I believe that if you do not specify the full path then VB.net or VB file uses app to create the file in the directory from which the application is running or in the common files folder. A best way to see whether a file is created is by using a msgbox step after the creation code.