Kind regards and hope this helps
• I'll be the first to say: Done properly, the above list of steps could wind up being an immensely daunting task, especially if the solution in question has even a moderate amount of complexity to it. I'm not trying to set you up with Herculean tasks -- I'm just trying to provide a high-level view of some of what I think it would take to do a quality job achieving the goal stated in your post. The above task list format can, unfortunately, be misleading -- Make no mistake: There is a lot of learning that has to happen before each step can really be completed.
• I've deliberately steered away from suggesting that you seek out some amazing tool that can accurately translate scripts from one environment to some other environment. If such a tool exists, it certainly would be amazing. Regardless of the existence of any such tool I feel that the steps above are important, because the knowledge that is required for each of those steps is the same knowledge that will allow you to make a well-informed and discerning assessment about the potential of any translation tool that you might come across.
• My guess is that your project is a port of a FileMaker solution of considerable size to another environment. The better that you understand FileMaker, the easier this will be, hence my emphasis above on starting with a certain level of proficiency in FileMaker.
• I'd like to encourage you to invest a little bit more into your forum post by perhaps adding some background to what you are working on, and what you have already tried and considered, etc.. I think that providing such background could help return some responses with more useful tips and guidance.
Thanks a lot.
Actually, the above strategy is already used by me for conversion and I was also successful in doing it. Now my priority is on is there any way or tool for automating it as manual work takes time. Is there any reference for this done so far?
There is no tool I know of
steve_ssh answer has the process of doing the conversion. Understand what the script does and do it in other environment with required programming skills.
abirami.jagan As you said, manual work takes time. It sure does. That's why FileMaker is a great tool for many cases we do (it takes a lot less time). But some tasks are easier to do in other environments. And that's why we can integrate with other solutions quite easily natively or by plugins.
How can I convert an apple into a banana? <- just as vague.
A few comments:
1) In your original post you made reference to converting FileMaker "script". In your most recent reply, you instead referred to converting FileMaker "calculation". Would you be willing to clarify that? There is considerable difference between what people think of when they read the term "FileMaker Script" versus the term "FileMaker Calculation". Some clarification of nomenclature could help reduce miscommunication about your project, and might yield more on-target replies.
3) Just out of curiosity: Is the target environment something like NW.js or Electron ? Edit: I just re-read your reply and saw that you said "console application".
Yeah, Its about Filemaker calculation and not script.
No, the target environment is different.
If just calculations, then FMPro Migrator might work
var str = "Manufacturing";
var res = str.substring(0, 4);
Or, just use an auto enter SQL Character Column, with a computed value, e.g. SUBSTRING( 'Manufacturing', 1, 4 )
It's a little un-orthodox, but it works :-)
gdurniak SQL calculation is one option but it's might not be the desired solution. It's worth to try if FMPro Migrator does it for you.
So one question is that what SQL db is it in this case?
SQL does have 'calculations' but mostly the raw data is stored. Then there are queries to make the temp tables with the SQL functions performing similarly to FileMaker Functions:
Retrieving data ...