I'm currently developing a system for our company right now and looking for some input.

The part I'm doing right now is the usual Company/Contact entry layouts. We generally deal with a specific person at a specific company, but we have to have the flexibility to set up multiple and default name/addresses as we often ship to different addresses/people under the company name.

The DB current is set up with multiple TOs as shown attached.

I am envisioning that as companies are first created, there won't be any addresses or contacts associated with it yet - so we want to click "Add Contact" or "Add Address" and it would pop up a layout to add a contact relating to the Company table.

Maybe I have archaic thinking? Is this possible or should I be approaching the data entry a different way? Any ideas would be welcome - I'm still in the layout design stage so no work will be lost if there is a better way!

Jason

Relations.pdf.2ffc94b936ff7e4c0cdc5a021129cbd2

I think your setup sounds good to me. One thing I noticed from your PDF was that you named the TO's with 'Entry' in the names. I would think you could use the same TO's for entering information or viewing it; since you are entering data in a new window.

I kind of like the idea of using a ContactInfo table related to Contact, which can hold an unlimited number of phone/email/fax/etc.

It would have text fields 'Data' and 'Type'; 'Data' would hold the actual phone#, or email, etc. 'Type' would hold the type of data: 'email', 'phone', etc. I haven't used this setup yet, but plan to on a system I an working on.

Interesting idea. I may borrow that for this one here..

You are right about the 'Entry' TO's. They will be able to add/view/modify, along with the other 'Entry' type TOs. I just wasn't sure what to call it : Maybe 'Mgmt'...

Anyway, the main issue I have is how to make a friendly UI for adding extraneous detail of a company (the contact, the addresses). I've been struggling with a popup layout method, and I think I may just resort to using Tab Controls on the company layout to add contacts, set defaults, etc. Still looking for any other input on this if any is out there!

I like using multiple windows in databases; which is why I said I liked the sound of your setup.

To add an address or contact, you would have the user click an "Add" button which runs a script:

set variable[$CompanyID]

new window

go to layout[address]

new record

set field[_kf_CompanyID value: $CompanyID]

If you wanted, you could make the window act like the 'Custom Dialog Window' in that it cannot be closed or minimized except by a 'Save' or 'Cancel' button on that layout. If your interested in that option, let me know.

You are right about the 'Entry' TO's. They will be able to add/view/modify, along with the other 'Entry' type TOs. I just wasn't sure what to call it : Maybe 'Mgmt'...

Why couldn't you just remove it?

Ooh, yes I would like the Custom Dialog Window for sure. There's nothing worse than people losing their windows because it lost focus by accident.

re: TO names.. If I removed Entry, I'd end up with Company__COMPANY, or Item_ITEM_REFERENCE.. a bit too vague for me. Or maybe vague is what I need? I am still new to developing FM db's.

I like using multiple windows in databases; which is why I said I liked the sound of your setup.

To add an address or contact, you would have the user click an "Add" button which runs a script:

set variable[$CompanyID]

new window

go to layout[address]

new record

set field[_kf_CompanyID value: $CompanyID]

If you wanted, you could make the window act like the 'Custom Dialog Window' in that it cannot be closed or minimized except by a 'Save' or 'Cancel' button on that layout. If your interested in that option, let me know.

Why couldn't you just remove it?

Dialog Window sample file attached.

I think what you called vague is a good thing; these relationships can be used for every layout/script/everything you make that accesses the Company and related information. Of course I am only looking at a small portion of your TO's, so perhaps there is a grander plan that I am not seeing. My only point is that these relationships can and should be re-used in many areas of your database.

I just posted some links to graph modeling (the first link), and Development Standards. I really find that having a set of standards to use when developing helps.

http://fmforums.com/forum/index.php/topic/75108-starting-over-insight-needed/page__view__findpost__p__355911

DialogWindow.zip