Hi FM talkers,
just to share something with you regarding this threat.
I posted a question to FM Butler for the bug I found in their
Occurrence Selector app, about dealing with spaces in the name of TOs.
I explained what I saw, and asked are they aware of that and is there
a way to fix that, or....
Look at the official response from Mr. Gekiere from FM Butler:
Quote:
Hi,
Thank you for your feedback.
It should work fine if you type fast enough :)
Best Regards,
Lieven Gekiere
:End Quote
Smile face, nothing about the issue I raised. I am trying to use
their app, I've found a bug, and what I get is "use FM relationship
graph and type fast as you can". Simply said, weird.
I googled Lieven Gekiere, and saw that he is a FM tech from Belgium.
It must be the European humor he used in his email, which I started
to miss, since I am originally for Europe (only the wormer southern
parts of it)
Your frequent FM talker:
Pavle Ancevski Pajo
New York Hotel Trades Council
[hidden email]
On Jul 3, 2009, at 11:12 AM, Colm Osiris wrote:
> Thanks for that, Pavle.
>
>> I found a small bug in it. It doesn't work if you use spaces in
>> your TO names (which we use a lot). I am not talking leading
>> spaces (which I am not using but rather spaces inside the name).
>> It shows everything fine until the first space in the TO names,
>> but after the first space shows random results.
>>
>> Eg. I name my tables as A_name, B_name etc
>> I name my main TO as A_Name, inner related TOs as "A to B to
>> D_blabla", and external db TOs as "A to xA to xF_blabla"
>
> I never use spaces in anything, table names, TO names, value lists,
> custom functions, or fields, or anything else. This comes from many
> years of programming BFM (Before FileMaker), when spaces in names
> was just not allowed, and it seems to me to be pretty good
> practice. All my names are made up of compound capitalised words.
>
> In TOs, I always name them like this:
>
> the base table is always called tXxxxxx, where the 't' stands for
> 'table'.
>
> The TOs based on the above table would always be called
> Xxxxxx_Yyyyyy, where tYyyyyy is the name of the base table it is
> relating to.
>
> For instance, to pick one at random, I have a TO in the current
> solution called
> 'ClientDept_ClientContact_Job_All@FindByJobTitleList_DisplayByAccount'
> . From its name I can tell exactly what tables it relates, and how.
> Sometimes the TO name elements have a 'g' suffix, which means
> 'global'.
>
> Without such a naming convention, in a solution of over 400 TOs
> (from an original 43 base tables), I would never know where I was!
>
> I'm sure other naming conventions are available!
>
> Colm
> _______________________________________________
> FMPexperts mailing list
>
[hidden email]
>
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au