-
1. Re: Merge two starter solutions
Heres a screen shot of what I've done so far. I also need table "products" to relate to table "estimate data".
-
2. Re: Merge two starter solutions
The White Paper for FMP Novices is useful
http://www.foundationdbs.com/downloads.html
Lynda dot com has Filemaker Videos (portions are free)
http://www.lynda.com/FileMaker-training-tutorials/116-0.html
Free unlocked templates are useful for examining design
Starting Point -
http://www.fmstartingpoint.com/
Donations -
http://filemakerdonations.com/
Recruiter -
http://rccrecruiter.com/alt-index.html/
Data4Life -
http://www.data4life.net/
A free calendar is available to be bolted onto your database
http://www.seedcode.com/cp-app/prod/calendarfree10/
You can search specific Filemaker sites on this Custom Google Search
http://www.google.com/cse/home?cx=001044389222327874554:vi8it1bulm8/
Looking at FMP business database demos is useful - some are fully useable
The Excelisys Business Tracker V3.0
http://www.excelisys.com/exbiztracker3.php/
Filemaker released a FMP runtime database in 2007 for students called "Campus Productivity Kit" and is available online, notably at CNet
Google "Campus Productivity Kit"
WIN http://download.cnet.com/FileMaker-Campus-Productivity-Kit/3000-2124_4-10577579.html/
Mac http://download.cnet.com/FileMaker-Campus-Productivity-Kit/3000-2124_4-10577567.html/ -
3. Re: Merge two starter solutions
What is the difference between an estimate and an invoice?
Where I come from we have something like a "Price offer" and if the client accepts, you do the work, and the price offre becomes an invoice.
But the two are exactly the same, and the only difference is that an invoice get's an invoice number and needs to be payed.
You could just add a "Type" field to choose wether the Invoice is an invoice or an "Estimate". And you could print a different kind of document according to what Type you have.
Also I see You make an Estimate Id Match field in the Estimate Data table, but you relate it to the Customer ID Match field. That might not be a good Idea. It should be related to the EstimateId.
If you want to link to products you simply make a number field in the Estimates Data table called "ProductIdMatchField" and relate it to the products table.
It's possible that you need to make a second table occurence of the Products table but that's not a problem. In fact it's better, that way everything remains nice and organized. Just make a second table occurence and call it "ProductsEstimates".