Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Stephen.S.

  • Rank
  1. I haven't done any web design or used XML/XSL, etc., yet I'm wondering if you created a relationship that returns a range of records using Start_date and End_date if you could use that?
  2. This simple example should help you get started. Writers.fp7.zip
  3. Brian: The Button would be on the Client layout. You wouldn't want to enter the Client information in Invoices because every time you created a New Invoice for John Doe, a new record for John Doe would be created in Clients. Hence, 10 Invoices for John Doe.. 10 entries for John Doe in Clients. You only require 1. The separate table for line items is because each Client can purchase more than one item on a single Invoice. To capture each item (line), you need a record (line item) for each. You have 1 client who you can invoice 1 or more times. This requires separate Invoi
  4. What you're looking to do is have the Invoice table look up information from the Clients table. This way if the person should move, change phone numbers, etc., the information does not change across all invoices associated with that client. Look at the attached file. Create a few new clients. Then click on the New Estimate button for the client you want to create an estimate for. The script simply copies the Client ID from Clients, creates a new record in Estimates, pastes the Client ID, etc. A lookup takes place pulling in the desired information. You can see a few fields of inform
  5. You're really going to need 4 tables; Clients, Invoices, Invoice Line Items (or just Line Items) and Services. In your Clients table, you would relate Client ID with Client ID in the Invoices table. The Invoice table should generate it's own Invoice ID which will be related to the Invoice Line Items table through Invoice ID. Services would be related to Invoice Line Items using a Services ID relationship. Basically, you enter the Client information in the Clients database. You will probably click a "New Invoice" button which will set a field in Invoices triggering a lookup of the
  6. I saw a similar problem to yours once. The only way to fix it was to delete the data, then reenter it. Not what you wanted to hear I'm sure. In any event, that was 6 or 7 years ago at least. I've never seen that issue since. The only thing I can suggest is placing the field in question on the same layout, but as a text field (next to the one formatted as checkboxes). Make the text box wide enough and tall enough so that you can see all the possible entries that are available in the field you have formatted to display as checkboxes. Now, whenever you check a box in the checkbox field,
  7. Thanks for pointing out the site. It would seem their website is in need of an update. Under system requirements for the plug-in, it states: Mac OS 7.6 through OSX 10.3 or later FileMaker Pro 4.1 through FileMaker 6. FileMaker 8 is also supported. FileMaker 7 is not.
  8. You could try giving the users a Print Selection menu on the layout from which they can choose the action they desire to accomplish, and thus the printer they desire to use. The attached example will of course need to be setup for each particular printer and the desired page setup, but should give you something to think about. Edit: Only the print selection scripts (List by Title and List by Sub Title) will actually output something. Stephen Printers.fp7.zip
  9. Walter, Threw the attached together rather quickly. First layout is the animals information (your master table). Here you can enter the animals basic information, as well as its weight in the portal below. The next layout is the Drug information. The third layout is used to display Weight and Dosage History. If you click on the Green rectangle in the portal on the first layout, you will be brought to the Dosage History record for that animal based on the particular weight chosen in the portal. On the Dosage History layout, click the red rectangle in the Drugs portal and it will apply
  10. Thank you both. Your points are well taken. I had considered Get(CurrentDate), yet became a bit concerned realizing the person may miss a day at work. Thus, any reminder(s) due on their day off would be missed the following day. For this reason, I'm using <=// with a flag. This should ensure all reminders due today or earlier with the flag not set will be found. Seems to be working okay.
  11. When writing a script (lets say to find all records with a reminder date of today), is there any advantage to using one of the two methods below over the other? I could use: Enter Find Mode Set Field [History::Reminder Date; "//"] Perform Find or, I could just use Perform Find and Specify the Find Request. Is there any instance when using one method would be preferred over the other? Thank you.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.