By Peter Wagemans
A customer is complaining about his FileMaker Pro 16 application acting up: when brought back from the background, the application requires the address of the server, even when the customer is actually logged in to the server. The customer took a screen shot of this, and the application window is clearly visible behind the nagging dialog.
Clearly again a FileMaker problem, but I'm not going that way anymore, since I have to make a living as well. I was just wondering what could be done to avoid the disconnect, and on reconnect, how to help FileMaker a bit reconnecting.
The first thing I was wondering about, was App Nap. There's a FileMaker help article here: using-filemaker-networking-on-mac-os-x-with-app-nap-enabled but the last edit is in 2015 and it covers only until 2013. The second google link FMP v14 and App Napp on the FileMaker Community web site seems to confirm that it is still an issue in v14. Why did FileMaker stop editing the article then? Apple has removed the check box option from the "Get Info" window of the application, one way of enabling/disabling it today is to use the excellent Onyx freeware application. But that switches App Nap system wide, not on application level. I'm wondering if it should be off or on, the customer uses the latest MacBook with Sierra.
The second thing is the password linking mechanism that seems broken as well on reconnect. You open File A, file A needs file B and FileMaker internally passes the credentials used to open File A, to open File B. Unfortunately this doesn't seem to happen on reconnect, and FileMaker asks for the password of File B, with no option to save the password, although this option is set in the file preferences. I made the customer open File B directly, and save the password to the keychain. At least this *should* lessen the annoyances he is facing today.
Does anybody have any insights to add here?
Hi. We have successfully created a Filemaker Server to Filemaker Server configured. When we tried to add another Filemaker Server to Filemaker server configuration, we got an error "You have exceeded the limit of 1 Filemaker Server to Filemaker Server configuration for this license." In our license, we can sync up to 2 configurations.
My client is using FM Server 14. On it I have a web form that is accessible to the public. It requires no user name or password...it's entirely open via guest login.
I have server scripts that import the data entered into a broader ticketing solution that is locked down. The tickets are then deleted in the guest-accessed file. We are now looking at upgrading to FM Server 15 and the new licensing model. I have a sinking solution that this kind of approach is untenable with FM's new paradigm.
Is this approach broken w/FM Server 15...requiring me to use something like Google Forms for data capture?
Is there any background information available on how the new FileMaker Licensing for Teams (FLT) works? And I don't mean the sales stuff that you can find on the FMI website.
I am very interested in differences between 'old style' concurrent licenses and the new FLT scheme, and what information is actually used to identify and validate a licensed user. There is a lot of confusion among developers on this matter and we need to advise our customers based on the right information, don't we?
First-time setting up a complex (or what I think is complex) database, and really could use some help. The idea is to be able to create an inventory of Computers, Peripherals, Software, and Software Licenses, (and where each is installed/located), along with the Purchase Order information for each item, and the Vendor for each P.O.
Here's how I sort of see it breaking down, but I'm confused as to how to setup the tables and relationships:
One Computer can have many Purchase Orders associated with it.
One Computer can have many Vendors/Manufacturers/Sales Reps associated with it.
One Computer can have many pieces of Software installed on it
One Computer may have many Peripherals
One Computer can have many Change Log entries associated with it.
One piece of Software (software title) can be installed on many Computers
One piece of Software can have many Licenses associated with it
One piece of Software can have many Purchase Orders associated with it.
One piece of Software can have many Vendors/Manufacturers/Sales Reps associated with it.
One piece of Software can have many Change Log entries associated with it.
One License can be installed on only one Computer at a time
One License can have only one piece of Software associated with it.
One License will have only one Purchase Order associated with it.
One License can only have one Vendor/Manufacturer/Sales Rep associated with it.
One License can have many Change Log entries associated with it.
One Peripheral can only be installed on one Computer at a time
One Peripheral can only have one Purchase Order associated with it.
One Peripheral can only have one Vendor/Manufacturer/Sales Rep associated with it.
One Peripheral can have many Change Log entries associated with it.
One Purchase Order can have many Licenses, Peripherals, and/or Computers associated with it.
One Purchase Order can have only one Vendor/Manufacturer/Sales Rep associated with it.
One Purchase Order can have many Change Log entries associated with it.
One Vendor/Manufacturer/Sales Rep can have many Purchase Orders associated with them.
One Vendor/Manufacturer/Sales Rep can have many Computers associated with them.
One Vendor/Manufacturer/Sales Rep can have many Peripherals associated with them.
One Vendor/Manufacturer/Sales Rep can have many pieces of Software associated with them.
One Vendor/Manufacturer/Sales Rep can have many Licenses associated with them.
One Vendor/Manufacturer/Sales Rep can have many Change Log entries associated with them.
Change log is: A manually-created list of notes for any changes, upgrades, problems, maintenance events, etc. performed for the entire department. Needs to be filterable/sortable by Date, Computer, Peripheral, Software, License, P.O., Vendor, and/or type of event. Event types would be from a manually-created value list.
Would be great if I could have a layout specifically for entering these events. Also, not sure how I would go about entering events if one event affects multiple computers or peripherals at the same time. I might have to just make duplicate entries (one for each piece of equipment) to link an event to each piece of equipment it affects?
I've begun setting up tables for:
- Installations (join table joining everything?)
- Vendors/Manufacturers/Sales Reps
- Purchase Orders
- Change Log (not sure what fields I need in this)
I'm also trying to figure out the Primary Keys and Foreign Keys, how the relationships should work, and how I can create a layout for let's say Computers that will show me:
- Computer info (computer name, location, hardware specs from the Computers table)
- P.O. number for Computer (from the P.O. table)
- List of installed licenses (including software name/version, license number, vendor, and P.O. associated with that license) (portal to the Licenses table, filtered by ComputerID?)
- LIst of installed peripherals (including the type of peripheral, manufacturer, name/serial number, vendor/P.O., date of install) (portal to the Peripherals table, filtered by ComputerID?)
- Change Log list for that computer, sortable by date and/or type of change. (portal to the Change Log table, filtered by ComputerID?)
And a layout for Software that will show me:
- Software name/Version
- Type of Software (standalone software, software plugin, etc.)
- List of Licenses associated with this Software (including software name/version, license number, vendor, and P.O. associated with that license) (portal to the Licenses table, filtered by SoftwareID?)
And a layout for Vendors/Manufacturers/Sales Reps that will show me:
- Vendor Contact info (sales rep name, phone, email, website, etc.)
- List of P.O.s associated with this Vendor, sortable by date, and expandable to see the individual items within that P.O. (such as license numbers and where those licenses are installed, or peripherals and where those peripherals are installed)
If anyone has any advice, I sure would love the help. Thanks.