Search the Community
Showing results for tags 'external data'.
Found 2 results
All files/tables in this discussion are fmp12 using FM 17 and both files are opened when initiating the app. "logging" is opened as the primary file and "claims" is opened as an external data source. I have a table called "newclaim" in "logging" which contains mailing address information including a USPS zip code. I have a table called "lu_ZipCode" in "claims". There is a relationship set between "newclaim" and "zipcode" on a field called "COID" (company ID). This field is automatically populated in both tables with "DCSI". This is an old method (used in Fm6) of establishing a simple relationship so that global fields can be used to pass parameters into scripts for zip code lookup and verification. In the parent script (in "logging") I set the related field "lu_ZipCode::_gZipCode" with (for ex) "12345" with the intent of calling a subscript in "claims" then using "12345" to do the lookup. However when the subscript is called the "_gZipCode" field is empty. As a workaround I called the subscript passing the "12345" as a parameter which of course works as one may expect. After setting the parameter to a local variable in the subscript I'm able to do the lookup then populate the global fields "lu_ZipCode::_gCity" and "lu_ZipCode::_gState" while still in the "claims" file. Yep, sure enough when I go back to the parent file the global fields I just populated are empty. It's worth pointing out here that prior to yesterday "zipcode" was a separate file and the methods described above worked like a charm. This effort is being put forth to consolidate this old FM6 solution with 40+ files into just a few files. I imported "zipcode" into the "claims" file then copied and modified the scripts anticipating that this would be a quick little project to get rid of one more file. I know there are better methods (ie JSON) to get this done and I will probably go that route. At the same time I'm left scratching my head on why this tried and true method doesn't work. Why would global fields I can populate from one side of the relationship not be populated when viewed from the other side?
Hello. I am not sure this is the right place to ask about this - perhaps it needs to be in logic layer section - but thought I would start here. Note: I only have access to FM11 Pro In my office we use several Filemaker databases for various teams. They work great and are customised to the needs of each team. The problem is this. Currently our reception opens up new entries for each DB as needed. Because we have 3 separate databases they have to open each one as needed and add a new record. I have been asked to find a solution whereby the databases do not change for the back-of-house teams but our reception gets a single screen from which they can create and search each of 3 different databases. I have some ideas for implementing this but thought I would get some advice before setting this up. There are two main approaches I have thought about. Create a small Database that opens each of the 3 other databases in a small popup window. Then in each of the backend databases I put some scripts that make sure reception cannot stray into the wrong area and the window is forced to close when they are done adding a new entry. Access tables from each of the 3 backend databases directly in my reception database. Then I could just build some custom layouts and scripts for the front desk and leave the backend systems unchanged. The second option appeals to me more as it should keep all of the reception's needs confined to the one database and I would not need to have logic spread throughout all the backend systems, however, I am not sure how to achieve the second option. Are either of these approaches possible or a good idea? Are there better options? thanks