Ben Moore

I am trying to create a list of dates from multiple tables to create a gantt chart. My projects have Shipping dates, Installation dates and task item dates. Each of which come from their own tables. Is there a good way to import all of these dates into one table related to the project, each with it's own record of Start date and end date. I'd rather have: Project | Item | Start_Date | End_Date| than: Project | Install_Start_Date | Install_End_Date| Ship_date | Ship_Arrive_Date | Task_Start_Date | Task_End_date

I ended up creating "Estimate Prefix" independent of the "Estimate_ID" field. This is an autogenerated serial number. When I create a revision, the prefix is copied and the serial number is reset -1, so the next NEW estimate is still in order. I did the same thing with the "Revision_#" field I created.

Often we have to revise estimates for a customer, and they may come back and order against an estimate that is not the most recent. I am trying to find the best way to tie all the estimates together with the same Estimate or Job #, and increment a revision #. So far I've created a Job# field, and a Revision number field, but having trouble getting the revision number and job number to increment correctly when I have a new estimate vs a revision. Any suggestions?

I am a distributor. My customers can also be distributors. They can also be large companies with many locations and hundreds of contacts, like Pepsi. Is it wiser to keep the "Accounts" table as is with only one "bill to" and "ship to" address and really treat accounts as locations, or create a separate table for "ship to" addresses and associate them with an account relationally? Has anyone else with this sort of customer relationship found a succesful solution. I simply don't see the efficiency of having to store the same contact and billing information for 50 different locations for all my larger accounts. For instance accounting personnel, regional and district managers etc are connected to many locations under the same "account".