I have 2 runtime solutions. Solution B has a script to import data from Solution A.

Since I do not know where users place their respective runtimes, I end up with my script always asking to locate runtime A.

It would be easier to instruct users to place both runtime inside the same folder.

But If I do so, opening runtime A works fine, however opening runtime B will still open runtime A. I can't access runtime B.

I also ended with the opposite result, where only runtime B will open.

Both solutions have their .USR and their .exe There are also countless small files created with each runtime. They all have the same name and size, so I have to keep one copy only of all these small files.

I tried binding, but with the same result.

Either I am constantly making the same mistake, or it can't be done. I wasted countless hours trying to achieve this.

Any hint?

AFAIK, the .dll and other "small files" are unique to each runtime.

I would place runtime B (with all its associated support files) in a subfolder of runtime A, and have my script use Get(FilePath) to find it. The calculation would be

Left(Get(FilePath) ; Position(Get (FilePath ) ; Get(FileName); 1; 1) -1)

If this calculation is executed in runtime A, it returns the folder which contains runtime A terminated by a "/"; you would add & "subfolderName/runtime B" to it.

I would also recommend that you use an installer compiler such as the freeware Inno Setup to install your solution where YOU want it installed on the user's system, and prevent it from being put somewhere where FileMaker does not have write privileges

Thank you for the information. I will try and test it in the coming week.

However, my script resides inside runtime B. Is the ''calculation'' really executed in runtime A?

SD

If the script is in runtime B, then it will return the folder enclosing runtime B. If B is the parent db and A is merely a data source, then A should be in the subfolder.

The calculation only gives the path. Most often, you would set a variable $fileA to that value, and then the next script step would be Open File( Open hidden; $fileA)

If A is indeed only a data source, it might be a whole lot easier (and much more compact) if you exported the data to a merge file, and distributed that to your users, rather than another compiled runtime. Your script would then use Import Records .