asked on FM - Design & Strategy Advice for new DB
We have two businesses - property management and a realty company - that share Filemaker. Leads are passed by email from the first group of salesmen to the 2nd after 21 days. Now, now my boss wants to create a new db or table on the realty side to import the new leads from the P.M. side. However, we already have a contacts table on the realty side (ongoing relationships only, not Leads). So, would you a) combine the leads imported from P.M. to Realty with the current contacts in Realty into the same table and just flag them differently or b) create a new RealtyLeads table and when a lead becomes a real contact, import it in from RealtyLeads to RealtyContacts? The drawback of combining is that the fields and design are a bit different and the Contact table woujld grow tremendously because we receive about 20 leads per day.
No right answer here, just looking for advice.
No right answer here, just looking for advice.
FileMaker Pro
Last Comment
rvfowler2
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
So unstored calcs only slow down FM when displayed. Does that mean I could use them behind the scenes and they only get calced when used for a weekly report?
Yes, that is my experience.
ASKER
Thanks.
We have seen FM slow down a bit with the growth, since I've been here (about 14 months). We've added one db and about 20 tables. But possibly where it slows down is not the increase in records, but the use of unstored calc fields. I've posted this in another question, but I think we use too many calc fields when we could use a report instead.