Jump to content

William Slim

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About William Slim

  • Rank

Profile Information

  • Title
    Filemaker Developer
  • Industry
    Software Development
  • Gender
  • Location
  • Interests
    Software, Music, Music Technology, Markets, Snooker, Golf

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Dave, Thanks for your explanation. I should have said what I was trying to do: After initial analysis of a DDR for a system I'd like to say to a client: "We've found 'X' issues in your system that may need fixing/investigating" - initially I thought the Report Card did this, reconsidering, and from what you've said, I see the Report Card (broken references) shows the number of actual items affected - (counting unique instances of script names seems to confirm this). Also caution should be taken when looking at say: Impacted Layouts 0% (there may be many layout object issues
  2. Hi all, Figures for broken references differ completely on the Report Card vs the 'Broken References' node if FMPerception. Some figures, such as 'Impacted Layouts' are empty in the report card '--' yet may have '24' in the Broken Refs node. What is the difference between them/how should they be interpreted? I'm guessing the node should be relied upon but I'm having difficulty tying up figures between the two even at a headline level. In this particular instance: 'Fields Impacted' on the report card states '15' yet <Field Missing> and 'Empty Field Reference' are both in t
  3. Update - I've tested from two new devices: 1. additional iPad (FM GO 15) over my mobile Wifi network - FAIL 2. New Windows2 machine* (same network as Windows1 - FM15) - FAIL *the original Windows machine (same network) still connects fine. I should add that this server is the limited Dev server obtained via the FM community membership. It should accept up to 3 FM client connections & 1 Webdirect / FM Go but I've closed all when testing to be sure.
  4. Hello all, I'm having an issue with my Macbook air seeing 'Connection Failed' for only one dev server, despite other devices being able to see it. Setup as follows: Macbook Air: FM 14 & 15 - able to see 2 AWS dev servers + 1 client server (via vpn) - Personal AWS Dev server = CONNECTION FAILED Windows 7: FM 14 & 15 - able to see all of the above, no issues Ipad 3: FM Go 14 & 15 - able to see all of the above, no issues --------------------------------------------------- The Mac OS is Sierra and the Dev server it won't connect to is now running FMS 15 (
  5. I think I've got it, though correct me if I'm wrong. I've gone through the DDR but this didn't really help in this instance, the iPad scripts are not used on the desktop, the key seems to be that although the TYPE MATCH FIELD is set to auto enter $$CURRENT_TYPE, (which is empty via desktop) 'Do Not replace Existing Value' is unchecked which means when a new record is created in the Data table via a portal, the value is pulled via it's relationship (the Global Match field in Research Notes table)
  6. Now I feel like a fool, as I suspected I would. That script folder was collapsed but a script under it made it look as if expanded. Though I didn't expect iPad scripts to be active on the desktop - not thinking laterally. Thanks Steve, I'll now study the database design report further.
  7. Hello all, I'm hoping one of you might be able to solve my little mystery! I've been using and modifying the Research Notes Starter solution, I find it very interesting dissecting these. I've sussed out most of the function but the $$Current_Type global variable baffles me, it's used as an auto-enter for the 'TYPE MATCH FIELD' in the 'Data' table which is then used as a match field to separate data into it's relevant portals; Notes, Media & Documents. Depending on which portal you create the record via 'TYPE MATCH FIELD' is populated with one of these 3 types directly from the $$Curr
  8. Many thanks Bruce this is slick, I really like the button bar with hidden buttons solution so that's what I'm currently using in mine. Thanks to all who contributed here. I looked further into everything mentioned and for anyone on my level reading this here's some interesting links I ended up reading: Transaction based data entry: http://www.modularfilemaker.org/module/transactions/ https://www.geistinteractive.com/filemaker-transactions/ Edit dialogs with rollback: http://www.soliantconsulting.com/blog/2012/08/easy-filemaker-modal-edit-dialogs-full-rollback-support Advanced Fil
  9. Ok maybe I'm missing something, when I try and create a record using a script via a popup or popup button in the same table (not via a relationship or portal) the popup cancels before any data can be entered. If I use a script to make the popup persistent, the 'create new record' script step can't run because it requires moving away from the popup. But point taken, you guys have given me plenty to read and think about and I don't wish to sound ignorant so I'm cracking on with my build to get some more experience in the new version. I'll upload a file if I hit a wall later on. Cheers guys
  10. Thanks for the research tips BruceR, I did just that and found the 'Invoices' example an interesting learning curve. I also re-read some Filemaker transactions info, which actually made more sense than it did the first time around so I have plenty to consider and will continue to reference these things as I build. I'm certainly no guru so readily admit that I have much to learn, but am excited by the prospect! However I think my initial point still stands, the project I'm working on has perhaps the simplest initial data entry requirement possible, creating records requires several pieces of
  11. Hello peeps, I'm just getting to grips with Filemaker 14, skipped 13 so this is the first time I've had the opportunity to play with the popovers which I've been much looking forward to. I have to admit that I'm a little surprised that data entry hasn't been made much easier with the advent of popovers. Creating a data entry interface is certainly easier and looks good too, but the process of entering new record criteria and confirming or cancelling the process is much the same. Currently I use global fields to place on a popover and when data entry is confirmed scripts will: Copy the ent
  12. It's been a crazy few weeks for me so this has been on hold until now but I've been reading back through this and realised that my problem description could have been a lot more precise & simple, yet guys your responses, wow, above and beyond! Thank you so much. I have considered the solutions here and now realise I can almost definitely achieve this in more ways than one using your ideas. I'll report back with some notes on the solution I use - Thanks again!
  13. Yeah pretty much, but not just move a value, rather the whole field and all contents; let's say a field called 'Start Date' was imported into Spare52 in FM, I get instruction that 'Start Date' needs to be in ImportantField1, I want to hit a button type in 'Start Date' the script finds which FM field that's in (Spare52) then Show All records and move the entire contents to ImportantField1. Note: Because the data we import comes from other systems, we always have a header record. So I'll search for 'Start Date' on the header record and all other records will actually have dates in that field.
  14. Thanks for the file dwdata, that's pretty cool and I think I can use that for another solution to a different task.
  15. Comment & dwdata, thanks for your responses. In fact I do only want to scan fields from the first record! ie the header of the imported set. I'm not attached to using Quick Find it just happens that this function does half of what I want to achieve. Sorry I wasn't clear before, let me try again - Say for arguments sake our DB has 40 agreed/predefined meaningful fields and 50+ fields that are always in flux. In Filemaker we've created & labelled the 40 agreed fields as appropriate, Name, Address etc. The other 50+ fields are simply labelled Spare01 to Spare50 because what will be
  • Create New...

Important Information

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