I suggest that you keep all your data in the same tables of the same file. That will eliminate the need to transfer any data when the customer renews.
Why do you want to start over with an empty copy of your file?
When a customer renews it sets a lot of options back to 0 (# of referrals, amount of prepaid credit, ect.) all information I would like to keep from last year so that I can compare at the end of this year.
All of that can be done without having to start with an empty database each year.
Is that simply by saving a copy of last years information and then resetting for this year? How do I look through all the orders for this year and not see all the orders and payments from last year? And if someone does not renew should I just delete them? Do I need to make a Date box and only look up orders for 2013?
Is that simply by saving a copy of last years information and then resetting for this year?
That is what I strongly recommend that you NOT do.
How do I look through all the orders for this year and not see all the orders and payments from last year?
Find criteria, sorts, relationships and portal filters can all be used to identify which records are for a given year and can be presented to the user so that they only see the data for this year or any year they choose to specify.
And if someone does not renew should I just delete them?
A status field in your customer record can identify which customers have an up to date renewal status.
Do I need to make a Date box and only look up orders for 2013?
That's more in line with what I am recommending, but there are many ways to control which sets of records are brought up on a given layout.
Thanks! I'll play around with it and see what I can do.
I am trying to create a script that will track only orders for 2013. My script is: perform find with the criteria Orders::Date Ordered >= 3/1/2013. It finds all the correct 2013 orders but it is also finding about 12 other orders from 2012 and I don't know why. My "Date Ordered" field is set as a date. I have the same problem with my Payments table. My criteria for the find is Payments::Date >= 3/1/2013. It shows the 2013 payments and then a small handful of the 2012 payments.
It's hard to say without a more detailed description of your layout and what exactly you are doing. Posting the script you are using would be helpful.
To post a script to the forum:
- You can upload a screen shot of your script by using the Upload an Image controls located just below Post A Answer.
- You can print a script to a PDF, open the PDF and then select and copy the script as text from the opened PDF to your clipboard for pasting here.
- If You have FileMaker Advanced, you can generate a database design report and copy the script as text from there.
- If you paste a text form of the script, you can use the Script Pretty box in the Known Bugs List database to paste a version that is single spaced and indented for a more professional and easier to read format.