Jump to content

Sara Severson

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sara Severson

  • Rank
  1. Never a silly question... Running Server doesn't eliminate record-locking. If one user is actively modifying a record, and another user tries to do the same, the second user will get a message noting that User A is modifying the record, and it cannot be modified right now. However, there are many benefits to hosting a file on Server versus FileMaker client: - Access to more users. I believe only 9 users may connect to a file hosted by FileMaker client, whereas FM Server allows for 250-999 connections (depending on whether you're using Server or Server Advanced). - Server a
  2. Tip: Here's a hugely annoying aspect of the "Show Custom Dialog" script step. I recently wrestled with it and thought I'd post the tip in case anyone else is stuck. When including fields in a Custom Dialog (e.g. "Please enter the amount of whatever you're doing" [amount field]), the data the user enters in that field WILL NOT BE RETAINED unless "OK" is the default button. I had switched the default to "cancel," and kept losing the field info. Switch default to "OK," and option 2 to "cancel," and the info will stick around.
  3. I believe it's just a clarification of the same functionality. ("Previous record" is vague enough that it could either mean "previously visited record" or "previous record in creation sequence.") What do you mean it's not working for you?
  4. Hi Rob, For a simple layout, you could always employ the "Set Sliding/Printing" options to slide layout objects up based on the length of their content. However, it sounds like you're describing pulling lists of names from different tables... If your users are primarily using this layout live in FileMaker, you could use portals to show those names by category. If you want it to be more print-friendly, though, have you considered a subsummary report? Hooray for you for using FM10: now your subsummary reports can be beautiful and editable in browse mode (whereas previously th
  5. Hi, Make sure when importing that you only have "Add New Records" checked, not "Update Existing Records" or "Update Matching Records." This should eliminate any over-writing of information (turning previously closed records to "open"). I'm not sure why the auto-enter of "open" wouldn't always work, though. The field is defined to auto-enter Data? Do be sure to check the "perform auto-enter options when importing" box, during the import dialog. If you're spotty on this step, it would explain inconsistent data.
  6. It sounds an awful lot like FM is interpreting the field as Text. Double-check that the field is defined as type = Timestamp?
  7. Hope the posts above help with the immediate shutdown problem. To answer your other question (re: upgrading to 10 vs. just upgrading to the newest version of 9), from what I've seen I'd stick with the same version as your client machines are running. FMS 10 is great, but I've heard of some unpredictable behavior when FMS 10 is serving FMA 9 clients.
  8. Hi joniraincloud, Have you used "Set Sliding/Printing" already? I'm not sure about quickly setting two columns, but this may be an alternative solution: - In Layout mode, select the field in question and all elements below it. - Go to Format, Set Sliding/Printing. - In the dialogue box that pops up, select "Slide up based on all above." In layout mode you can make the field as large as you think you'll ever need it. Then, regardless of the size of the contents of that field, the bottom of your layout will slide up to fit (when printed or in Preview mode only).
  9. It's not hard to combine elements and include your Stock_pk as part of your visible key: Set your serials to start at 2000 and 6000, and have a separate calc field that would add your "Y1" to your pk field. However, because you'll be restarting the 2000/6000 sequence each year, I don't think this is a good idea. For development purposes, it is a best practice to have a unique key for each record. If you reset your key serial to 2000/6000 each year, you'd certainly run into problems there. You can still use the same technique (serial plus calc), but I recommend maintaining a separat
  10. Hi innodes, Dates in FileMaker are stored as the number of days from 1/1/0001, so if you keep that in mind you can use them in calcs just fine. i.e. you can subtract one date field from another date field, and the result will be the difference in number of days (if you return the result as a number). If your work flow is that something occurs 15 days after a date of origin, then 30 days, etc., just calculate those dates by: [origin date field] + 15 [return result as date]. You'll end up with the date 15 days after your origin date. Is that helpful, or do you have somethin
  11. Is there any additional layout-based formatting of those fields? For example, sometimes users will experience a delay in refresh if the field is formatted to display as a drop-down menu. Also, are Web users unable to view information in those fields at all times, or is it just that their edits aren't immediately visible?
  12. Hi, yep, that's good information. I'd recommend scripting an "Import as Picture" button, and do NOT store the file as a reference. (As long as the files are small, storing the actual file in the solution will circumvent the problems that arise when a user may move that file to a different location on their HD later.) The deal with displaying the image: If it's inserted as a File ("Insert File,") the image won't automatically render. As long as you use the "Insert Picture" script step instead, you should be golden. Best of luck!
  13. There are lots of options for this... You could use container fields with upload buttons, where you'll have to decide whether to store the files within the database or just store a reference to the file. I've also used the plugin SuperContainer from 360works with great success, for displaying image files within web viewers. It really depends on a few things: - What kinds of files will the users be uploading? - How local are your users? - Where will the files live? (On a shared server, or are they on disparate machines?) - How many files do you expect to be upload
  14. Actually, if you don't mind serializing the field, FileMaker will do this for you. When defining the field, just put your alpha prefix in front of the number in the "next value" area, i.e. "D1005." When the next new record is created, that field will increment up to D1006.
  • Create New...

Important Information

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