Help wanted with Filemaker Pro scripting ...

I don't get it ... It seems to me as if, by catering for non-
programmers, they've actually made it near-impossible for a programmer
to understand ... "layouts" ? who needs layouts when nothing needs to
be shown on-screen ? Why no SQL ? Cursors ? How does one do something
like cursors in Filemaker Pro ???

Is there a Rosetta Stone somewhere with "Sane SQL / RDBMS concepts"
translated to/from "crazy amputated Filemaker Pro scripting "language"
concepts" ???

On 2011-02-18 08:57:20 -0800, LinuxCub <linuxcub@email.dk> said:

> Help wanted with Filemaker Pro scripting ...
> 
> I don't get it ... It seems to me as if, by catering for non-
> programmers, they've actually made it near-impossible for a programmer
> to understand ... "layouts" ? who needs layouts when nothing needs to
> be shown on-screen ? Why no SQL ? Cursors ? How does one do something
> like cursors in Filemaker Pro ???
> 
> Is there a Rosetta Stone somewhere with "Sane SQL / RDBMS concepts"
> translated to/from "crazy amputated Filemaker Pro scripting "language"
> concepts" ???

If Filemaker isn't the right tool for the job, don't use it.

If it IS the right tool for the job, or the one you've been mandated to 
use, don't waste your time complaining that it isn't the only tool 
you're familiar with. Trying to run a table saw with the directions for 
a drill press isn't likely to make anyone happy, or to get the job done 
sooner.

Consider hiring a professional developer to help you get familiar with 
the concepts of Filemaker, or attending a training class or even buying 
a training DVD course. The tools available are quite powerful, and FM 
has repeatedly been demonstrated to be among the fastest 
development/prototyping environments out there.  Much faster and 
cheaper than *any* SQL system in the hands of a FM pro.

The truth is, there are things that SQL can do that FM should never 
come near. But FM can do certain things with extreme ease that are 
harder than hell in SQL. Tradeoffs, always.

It is possible with FM10 or 11 to use SQL with FM tables as the target, 
but you'll work faster, farther and much more effectively by using 
native FM tools properly. You don't need layouts if you don't need to 
show anything onscreen, but you do need CONTEXT. Cursors are managed 
with Go to Object or Select commands. Script triggers work off a 
reasonable but still limited number of object states.

So my recommendation for you is the same I'd give anyone faced with a 
new tool. Educate yourself on the use of the tool as it exists. Don't 
waste your time complaining that it's not That Other Tool. Recognize 
that even a skilled professional in That Other Tool cannot instantly 
become an expert user of This Tool. Realize that an experienced 
developer can make This Tool do things you can't even imagine.

If you're going to wear ice skates into the swimming pool, don't 
complain when you can't do the breast stroke.
-- 
Lynn Allen
--
www.semiotics.com
Member FBA
FM 10 Certified Developer

On 2011-02-18 12:58:40 -0800, LinuxCub <linuxcub@email.dk> said:

> My employer has, for lots of reasons, forced me to use FM.
> 
> I'm not (quite) complaining that FM is not That Other Tool.
> 
> I'm complaining about the fact that there seems to be no suitable documenta
> tion that teaches FM in terms that someone used to C / C++ / Embedded SQL e
> tc. can easily understand. Well, at least so far my Google-searches have go
> ne unsuccessful. Surely, I'm not the only one with such previous experience
>  ?
> 
> An example of the disconnect between my previous experience and FM:
> 
>   Filemaker has a "next record" type command, but it takes _NO ARGUMENTS_
>   So that has to mean that I cannot have nested loops or multiple "cursors"
>   (because I cannot specify which g*ddamn cursor I want to move forward)
> 
> And the documentation I've found on filemaker.com has nothing to say about
> this.

Go To Record, if you have to move through records until you hit one 
that meets a certain condition, is put inside a Loop, with an Exit Loop 
If test.  So pseudo-code in the Scriptmaker would look something like 
this:

Loop
	Exit Loop If [test goes here, for ex. Invoice Status = "Paid"]
	Go to Next Record/Request [Next, Exit after Last]
End Loop

That's where you put your arguments. You can also use Go To Record by  
number, or if you know or can calculate how many records forward you 
want to jump, there's Go To Record by calculation.

I highly recommend a third party FM reference, such as
http://www.amazon.com/FileMaker-Pro-11-Missing-Manual/dp/1449382592/ref=sr_1_1?s=books&ie=UTF8&qid=1298068243&sr=1-1

which 

gives an easy way to look at the useage and syntax of functions and a 
basic map of how to get there from here in FM.

I'm not aware of a SQL -> FM developers manual, because frankly, most 
FM developers started out as creative or business knowledge experts who 
built something in FM and somehow ended up FM experts who make a living 
at it. I know dozens of FM developers personally, and I can think of 
TWO who have computer science degrees. Many FM developers teach 
themselves SQL. Very few people go the other way, though some do. But 
those people who start with SQL and branch out or transfer to FM teach 
themselves, just like those who start out in business or creative 
industries.

In spite of the enormous installed base of FM, there are no formal 
classes in any educational institution I'm aware of that teach FM. It's 
pretty much learn on the job. Sorry. There are training programs that 
will teach you the basics, and at least get you up and running.

Look at it this way, the good news is that good data structure is good 
data structure no matter what tool you use. Once you've got that 
licked, the rest is details and a good reference manual.
-- 
Lynn Allen
--
www.semiotics.com
Member FBA
FM 10 Certified Developer

In article <4d5ef560@news.bnb-lp.com>, Lynn Allen <lynn@NOT-semiotics.com>
wrote:

> On 2011-02-18 12:58:40 -0800, LinuxCub <linuxcub@email.dk> said:
> 
> > My employer has, for lots of reasons, forced me to use FM.
> > 
> > I'm not (quite) complaining that FM is not That Other Tool.
> > 
> > I'm complaining about the fact that there seems to be no suitable documenta
> > tion that teaches FM in terms that someone used to C / C++ / Embedded SQL e
> > tc. can easily understand. Well, at least so far my Google-searches have go
> > ne unsuccessful. Surely, I'm not the only one with such previous experience
> >  ?
> > 
> > An example of the disconnect between my previous experience and FM:
> > 
> >   Filemaker has a "next record" type command, but it takes _NO ARGUMENTS_
> >   So that has to mean that I cannot have nested loops or multiple "cursors"
> >   (because I cannot specify which g*ddamn cursor I want to move forward)
> > 
> > And the documentation I've found on filemaker.com has nothing to say about
> > this.
> 
> Go To Record, if you have to move through records until you hit one 
> that meets a certain condition, is put inside a Loop, with an Exit Loop 
> If test.  So pseudo-code in the Scriptmaker would look something like 
> this:
> 
> Loop
>         Exit Loop If [test goes here, for ex. Invoice Status = "Paid"]
>         Go to Next Record/Request [Next, Exit after Last]
> End Loop
> 
> That's where you put your arguments. You can also use Go To Record by  
> number, or if you know or can calculate how many records forward you 
> want to jump, there's Go To Record by calculation.

Another option could be to first perform a Find for the appropriate
records, then the Go To Record [Next] command will simply step through the
Found Set containing only matching records.




> I'm not aware of a SQL -> FM developers manual, because frankly, most 
> FM developers started out as creative or business knowledge experts who 
> built something in FM and somehow ended up FM experts who make a living 
> at it. I know dozens of FM developers personally, and I can think of 
> TWO who have computer science degrees.

I have a Computer Science (and Mathematics) degree, but other than writing
a few custom Mac applications, I've never really had any use for it.

"Real programmers" would of course be writting their own applications
using binary code, not mucking about with FileMaker, SQL or anything else
built by someone else.  ;o)


Helpful Harry  :o)