erol

I am currently a version 6 user. I have scripts that import data from MS Access. There are two limitations of v6 that I would like to ged rid of. And I am wondering if v7Pro solves these issues. I browsed the user manual for v7 but did not find what I need. The ODBC connectivity in version 6 does not allow me to use a parameter. In other words, I cannot run a parameter query. I cannot say, give me all rows where price > 5, where 5 is a value that my user entered. The second limitation is the script maker field mapping. V6 has the way of remembering the last field mapping you did when you record the script. Once you create multiple scripts you really cannot go back and debug the field mappings. At least I cannot. I happen to be an advanced programmer with various languages and tools and I find the script maker in v6 to be very limiting. Is there anyone who can comment on v7Pro ODBC and script making capabilities. Is v7 Pro sufficiently better than v6? Does one have to go to the advanced version to have robust ODBC imports and script making? I would appreciate your direction. Thank you Erol

I am importing several fields from an Access db. Most of these are calcuated fields. So I created the queries in Access and I do not have to worry about the calculations in FM. Issue: However, there is one calculation that cannot be performed in a single query. Question: What is the best way of performing calculations on the fly, during a script that contains several import record steps?. Is it possible to execute an import returning a value, and to store that value in a "memory variable" or an array to be used in a calculation? I appreciate your help. (I am using FM 5.5) Thank you Erol

I am using FileMaker 5.5. I have a script that has several 'Import Records [..]' commands one after the other with different queries. I would like to run these imports without dialogs. Problem: Properties, for example field mapping and the sql statement, of the first import command seems to overtake the others. I cannot have each of the import commands to have their own query setting. What is going on? What am I doing wrong? Thanks Erol