• Content count

  • Joined

  • Last visited

  • Days Won


BruceR last won the day on February 8

BruceR had the most liked content!

Community Reputation

147 Excellent


About BruceR

  • Rank

Profile Information

  • Gender
  • Location
    Redmond WA

FIleMaker Profile

  • FM Application
    14 Advanced
  • Platform
    Mac OS X Yosemite
  • Skill Level
  • Certification
  • Membership

Recent Profile Visitors

32,480 profile views
  1. In addition, there seems to be some confusion about runtime deprecation and what that actually means. It is still there now; it will still be there in the next version. At some unspecified point, even further down the road; it may in fact finally disappear.
  2. Very curious and unsupported conclusions. Among them; perhaps understandably; failing to distinguish between ExecuteSQL; and Execute SQL.
  3. This is still confusing and still jumping into the middle of something without describing the basics. Please begin by describing your data structure. What tables are involved; what does your graph look like.
  4. This is an XPOST by the way, from FileMaker Community.
  5. And therefore FileMaker Server will not allow it to be opened. FileMaker Server 15 does not open no-password files.
  6. No, it is not custom search order. It is custom sort order. You could do web searches for drag and drop portal sort. You will need to add sortOrder field (number field) to the child record table and you will need to sort the relation by this field. To begin using it, have it auto-enter get(recordNumber). Edit it by hand to control sort. Then learn from the available example files how to automate this. Example link:
  7. The upside of the record number symbol is that you don't need to define a field. The downside is that if you want to fit {{recordNumber}} into a skinny space; that is difficult. There are some stupid FileMaker pet tricks you can use to resize it but they break if you touch the field. So I often use an unstored calc field, defined as get( recordNumber); and place that on the layout.
  8. +1 for comment's comments. As for a field definition being more easily accessible. Do you have any awareness of the risks of doing that? I suspect not; or you would not have made the statement. Though maybe you just don't have anybody using this system. What happens when you're defining a field while users are entering data? What can happen to the integrity of the file? You want users out of the system when doing this. Thus your timeslot for accessibility is extremely limited.
  9. Answer: no. To a significant extent, it is about making it easy for volunteers here to see enough detail of the solution to be able to help and being considerate of their time. Having seen some of the detail of this solution, this is even more apparent to me. Playing twenty questions, revealing tiny unrepresentative and incomplete slices of a solution for us to review, preventing the company from operating on reliable data; those seem to be important considerations.
  10. Use and MD5 checksum field. (Result is text)
  11. Just drag the image or attachment to the bottom of the reply window. You know; where it says Drag files here to attach.
  12. This isn't really getting anywhere. Statements about trimming have been vague. It may be time to move on and tell the company to work with an experienced developer. It would be very helpful if you could post the file. Or a clone of the file. Or a print-to-PDF or screen shot of the (complete) field and table definitions.
  13. It would be very helpful if you could post the file. Or a clone of the file. Or a print-to-PDF or screen shot of the field and table definitions.
  14. A button can either be set up to make an immediate, single-step action. Or it can be set up to call a script, which takes that action plus does some other things. Set the button to call a script, which uses the set field action you're already performing, followed by: Commit Record Refresh Window [ flush cached join results] Note that it may also help to put a Freeze Window statement as the first line of the script.
  15. So this really has almost everything in common with a standard invoicing system. Customers, products, orders, order line items, prices. And as with invoicing systems, it is sometimes common for orders to consist of a standard group of products.