imoree

Because of this issue, i have now learned about pickers and selector / connector. filemaker has grown so much. thanks Wim Decorte.

Portal Filter calculation: IsEmpty ( GLOBALS::g_lookUp ) or FindWordPartsInText ( GLOBALS::g_lookUp ; Customers::FullName; 1) Issue is if i am creating a new record: the Customers information is not stored. Since Global searchfield is: a field in portal to trigger cf, then it does not find anything. see file attached: layout ( work order): Your Store.fmp12

the calculation gives me NO RESULT on the layout i need it for.

Hello Everyone; i am tyring to get a type ahead working on my system regarding point of sale. The only issue i see is taking teh user to another layout to use the following type ahead system: If ( start > WordCount ( haystack) ; 0 ; Let([ needle = LeftWords(needles; 1); word = MiddleWords(haystack; start;1) ]; Case ( Left ( word; Length(needle) ) = needle; If( WordCount(needles) < 2; 1; FindWordPartsInText(RightWords ( needles; WordCount(needles) -1); haystack ; 1) ); FindWordPartsInText(needles; haystack; start + 1) ) ) )

I would agree with that FItch.. Too much Custom Functions make it hard to read / debug and well, UNDERSTAND what is going on besides the person who wrote it.

Cartesian connection Shows all Records [X] from transactions to Model # It would help to see file though. eg; Model_ID [X] Model_ID (transactions table) would show all Model_ID's

M. Edoshin responded via an email list; here is pdf in its glory! http://dl.dropbox.com/u/9175169/Hierarchies%20in%20FileMaker.pdf

" Wrote an whitepaper on how to implement hierarchical structures in FileMaker 8 or above. " Here's the PDF and a sample FileMaker file. Link:http://edoshin.typepad.com/bits_and_pieces/2008/07/hierarchies-in.html is dead and M. Edoshin has not responded to my email attempts. thanks; -i

NO one chimed in : ( , but after some more working. Issue was using my global key as the value list Display data from: ( context ) the value list was getting "VALUES FROM" my Option TYpes::ID and OPtion Types::Name fields( Context ) i will figure this stuff out even if i go crazy trying to.

Hello Everyone; I am trying to do a prototype db , but i tell you context is a tricky thing that i still have left to master. If you look @ my screenshot i am trying to use a global to "SHOW" the Option TYpes from OptionTypes_select, but don't know HOW to! I have tested using lookup filelds and that works, but i would love to know how /if i can show data from Option Types & Options across the graph using globals within my Orders Table. The reason is i am wanting users to select and add certain criteria within Orders and after they make the selection, and choose Submit, the order is added to Lines, ONLY after they choose valid items. thanks for any assistance. -ian

Hello everyone; Looking for any help on this one; Having a bit of an issue with Connectiing Lines --> LineOptions-->Options ___Optionstypes. just wanted to know how to make this much more efficient jumping over to other layouts to create new records that relate accordingly or allow create wherever necessary. I am a bit hesitant for orphans so i need to figure out a delete tree as well Or perhaps just archive all my records in a utility table when necessary. Issue i have lies when on LinesOptions Table and user is adding option Types & Options eg. Product Type = Cake Option Type = Flavor Option = Pink Champagne. Now i need to create new LinesOptions record, which in turn sets lineOptions::optionsID to Lines::ID, then i need to go to layout Optiontypes; create a new record if it does not exist and set option:optionTYpeID to what OptionsTypes::id is. then go back to original layout to add another Product Option Type. I am collecing via globals from Orders Table. -any ideas or am i on the right track? thanks in adv. -ian

It is what You name it. object inspector. See under Name: that is where you name your "selected" tab in layout mode.

BCooney; have done some more work, Using GLobals to collect data for entry, Things are looking good right now. Thanks for your 5 cents! -ian

] test this: create a textbox in your Current table (name it Status ) now create a new Field ; call is c_checkStatus ( make it a textfield; with calculated value: Uncheck; if not replace... and enter Johns calc with your fields; Case( Name ="active"; YOURFIELD::ID ) Create value list based on this c_checkStatus. hope that helps

As you can see , this is starting to become quite ambiguous. Any ideas how i can eliminate this before this gets way out of hand? 1 Product can have MANY options, there are some Products which share the same Option( this is my issue) 2. using value lists, but perhaps this is not the way ! 3. Perhaps my normalization is not normalized enough? if not, how can i normalize better. Thanks -ian

I was talking of recursive data structures & thank you BCooney for pointing out to just contact Jonathan Stark. Here is the article; http://jonathanstark.com/fm/recursive-data-structures.php

Lots to read here: http://fmforums.com/forum/topic/80166-invoice-payment-portal/

Hello everyone; i have been searching this forum and have come across a few of what i am facing now Issues! They have to do with manufacturing and database design. Heard a few talks about recursive structure, but i have been unable to figure out what that means in its entirety via Google and books that i know where to look. Can someone please describe or provide links where to find more information/articles in relation to recursive data structures and possible manufacturing db models? TIA: -i

I like the idea of a picker per say, anyone else have other ideas? thanks Stephen , i am trying to learn what they did in that file http://www.excelisys...o-downloads.php. It definitely needs "studying" to make sure the implementation and desired affect is achieved> something that can definitely be ported as well. -i

It is manufactured upon request This adds a substantial level of complexity that i can't find easy examples of doing. Any that you may know of that are less extraneous or is that hierarchical structure. What about Entity attribute values-> i know these are hard /tricky to report on. EG> Entity : Handbag Attribute: Leather Strap Value: $15.99 thanks, -i

THe election of options affect the price. eg. If option 1 chose, $price increases basePrice by $15.99 etc.etc then the options are Added to the line items and price of option if calculated below to show final price with all options. Also, the ability to print / report will be ok once options are included in relations correctly thanks Stephen...

Add this script to your scripts: //Name the script GTRR //Name top portal "portal1" in object palette Set Variable [ $row; Value:Get (ActivePortalRowNumber) ] Go to Related Record [ From table: “models 2”; Using layout: <Current Layout> ] [ Show only related records ] Go to Object [ Object Name: "portal1" ] Go to Portal Row [ $row ] [ Select; No dialog ]

hello everyone; my first thing is i have a simple invoice system that looks basic like this customers -:Orders=: LineItems=: Products my issue is i add complexity as i have a few individual lineitems Products which have additional options. So i have to add another join table; LineItemOptions which connect line items to a product options table( another TO of Products) My thing is how do i make this more elegant or am i just being silly? Eg. User adds CustoM BAG ( product id, product TABLE) then they want to add another option(3) option1; leather strap with zebra print option2; color black with pink inlay option3; interior skin ( shark skin) After these options are entered , it connects to the lineitems table via lineitemoptions , but how to make this look more elegantly rather than 2 portals? Any ideas? TIA; -ian

When you give everyone the answer, no one learns anything! .. I know it usually just drags out the entire conversation usually huH!. Happy Tax days!!! -i

Heres a start; YOu can tweak to build a list using List Function and add a third param for qty http://sixfriedrice.com/wp/creating-random-numbers-in-filemaker-pro/ ; ia