Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


mr_vodka last won the day on May 11 2019

mr_vodka had the most liked content!

Community Reputation

76 Excellent


About mr_vodka

  • Rank
    Candy is Dandy... But Liquor is Quicker
  • Birthday 08/24/1976

Profile Information

  • Title
    Data Integration Specialist
  • Gender
  • Location

Contact Methods

  • Website URL

FileMaker Experience

  • Skill Level
  • FM Application

Platform Environment

  • OS Platform
  • OS Version
    Window XP, 7, 8, 10

FileMaker Partner

  • Certification
  • Membership
    FileMaker TechNet
    FileMaker Business Alliance

Recent Profile Visitors

10,134 profile views
  1. value lists you need an indexed field. Unstored fields are not indexed.
  2. If you want the filtering window to stay ontop, you can always use a floating window. As for wanting to click something in the filtering window and then that filtering the records in your main window, you should be able to script that rather easily.
  3. Sure look into the Max function and search across these forums and you should see many posts regarding similar serial number increase. That being said, do NOT use these type of indicators for your database keys.
  4. You shouldnt really have 6 containers for this. You already have a photos table. Just have a new related record for the 6 photos. As for your users not being able to edit the ones that are "default", you can do that with having a field in the photos table that captures the phototype. Then you can use that value to control what is a user added vs. "default" and the actions that one can take depending on that type.
  5. 40,000 records shouldnt be too bad. You could of course run a server routine that can gather the list into fields and display those utility fields.
  6. No idea what your structure looks like... You would have to have some sort of calculation to sum of each day. Please post more info.
  7. Have you tried deleting on the server? Also it may make more sense in your case to save a clone and import the data you will use going forward rather than delete if there are far more records to delete than save.
  8. Before you go down this rabbit hole of inventory, I would suggest you read about transactions. https://www.geistinteractive.com/2010/04/21/inventory-transactions/
  9. FileMaker Go connections will count towards the 5 max concurrent connections. That being said, it should have been the same with FM16. As for Peer to peer, it has been deprecated so it may make sense to start thinking of an exit strategy on moving your client over to server anyway. The new licensing gives you 3 copies of server.
  10. If it is just the starting stock or qty and EOD, why not just store the values in a summary table for daily records.
  11. Make sure that sharing is on, ports are not being blocked by firewalls, and each client has it's own license copy.
  12. databases dont really matter. You deal with table occurrences and then can be from the same table or a different database file. Post a copy of your file.
  13. Because it wasn't created efficiently for that. Keep in mind that you don't have control over the SQL statements that are being sent. FM interprets a user's actions and then tries to create a query to match what you are asking of it. Sometimes it is perfectly fine and other times very very inefficient, depending on what the structure and action given. It is best suited for ancillary activities to a core system IMO. Calculation fields created in FM in the shadow table of your SQL table will be unstored calculations and not indexed. It is better to create the calculation in the view
  14. Hi Pedro. What comment is saying is spot on. You may be able to get the result you desire but you may have to change the type of UI you use. You can search for "google type search filemaker" and you should come across many posts on the subject. Also quick finds will search all your fields. Perhaps this old thread can help you a little.
  • Create New...

Important Information

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