Jump to content

Ron Cates

Members
  • Content count

    566
  • Joined

  • Last visited

  • Days Won

    2

Ron Cates last won the day on September 6 2012

Ron Cates had the most liked content!

Community Reputation

8 Neutral

About Ron Cates

  • Rank
    member
  • Birthday 04/07/1969

Profile Information

  • Gender
    Male
  • Location
    Morristown TN ( Near Knoxville )

Contact Methods

  • MSN
    ron.cates@hotmail.com

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Windows
  • OS Version
    10
  1. Thanks. I'll give it a try. And I whole heartedly agree. Network issues are very difficult. In the last couple months since I have been providing remote access to this system I have gotten reports a variety of different experiences from different users in different locations. It's so hard to trouble shoot any issue when I can't reproduce what the user is reporting from my own location.
  2. User 2 reported this afternoon that she was able to open the interface file from the main file and it came up as it should. User 1 as of last night was still getting Table Missing on the Main file. Can't access the Sales interface file without having access to the main file so he get's no where. He will not be able to try again until tonight. Scratching my head..
  3. In this case the data file is the main file that is already open. The UI file is opened from the data file. The Main file is a self contained file that I have been working with for years. I recently developed and added the Sales file as a UI file that uses the main file as a Data file.
  4. Let me revise my response to bcoony. The UI file is opened from the main file by firing a script that then runs an external openning script in the UI file. Not sure if that makes a difference but it's not using an explicit open file command as the question asked. Do you think it would make a difference using an open file script step instead? rwoods I've double checked the External Data Sources and both files are connected to each other as External Data Sources using the relative paths ( file:CAMv1 and file:CAMv1_Sales ). The files do reside in the same folder on the same sever.
  5. The UI file is opened from within the main database using a script with an open file script step.
  6. I don't even know where to begin with this one. We have a quite large and complicated database developed continuously over the last 10 years. We are currently running Filemaker Server 16 on Windows Server 2008 R2 and all clients are using FMP 16, all on windows 10. Recently we have started working on allowing remote access to our system for employees on the road or working from home. Also recently added a separate interface file that uses the original file as a data source to provide a dedicated sales interface. Other than struggling with the performance over widely varying internet speeds the system has been up and running successfully. Until a few days ago... Here's what's happening. I am the developer and am located remotely. I do my development through team viewer but I can test the direct remote access. I am able to access the database remotely as well as open the separate interface file and all is well. User1 Accessing remotely opens the main database file and the fields all show "Table Missing". User2 Accesses the main database remotely and all is well but when she opens the sales interface file all fields in that file show "Table Missing". The system is operating normally for the 10 or so users at the local office. I have accessed User 2s computer remotely through team viewer and logged in to the database using my user name and password and I get the same result she does, so it's not based on the user account. So currently I'm looking at 3 different remote access locations all getting different results. We are all within the US and only a state or two away from the local office. I have rebooted the server this morning but no change. I don't even know where to begin. Any help would be appreciated...
  7. Jump on click

    I was experiencing this after upgrading to 12 I think. Anyway, what I found was that if my field borders were set to less than a full point it was causing objects to jump. For instance I had fields that were set with a border of .25 ( hairline ) . When I changed them all to a full point it fixed the problem. May not be your situation but something to check for maybe..
  8. Problem with File Path Variables

    You'll want to set the variable to the entire path and then enter just the variable $$marinaDir = "filewin:/C:/MarinaPro v17/Marina.fp7" Open File ["Marina"] (Marina File Path: $$marinaDir )
  9. unrelated locked formatting

    Nice. Hadn't tried that. thanks
  10. unrelated locked formatting

    Filemaker 16 got me with this one too if it's what I think it is. I had several fields that were formatted as a button as previously mentioned. In FM15 I could select the field and change the data source and such. In FM16 the options were grayed out and unavailable. What I realized as mentioned was that the field was now grouped. The easiest way I found is to right click the field and choose Arrange > Ungroup. I do find this annoying as I have to ungroup to make any changes and in doing so I lose my button setup. After the change I have to reformat as a button again. I often use some pretty complex script parameters so I need to be sure to copy them before I ungroup so I can replace them. It's not a big deal but less convenient than previous behavior.
  11. FM 16 Variable Repetition limitation change?

    I created a little custom function some time ago to allow me to set variables on the fly with dynamic variable names and repetitions. So to address my problem I just need to have the set variable script steps that are affected use this function to set the variables using the same repetitions as before. It simply wraps a Let function with Evaluate. The custom function is simply Evaluate ("Let ( $$" & ~var & "[" & ~rep & "]=" & Quote ( ~value ) & ";\"\" )") Parameters are ~var ( name of the variable ), ~rep ( repetition ) and ~value ~setVarByName ( ~var ; ~rep ; ~value ) So I can set my set variable script steps to something like this ~setVarByName ( "Back" ; Code ( Get ( WindowName ) ; GetLayoutID ) I've tested this and it works as expected.
  12. FM 16 Variable Repetition limitation change?

    The post on TechNet says 17 digits but I count 18. Am I miscounting or are they. Lol! Regardless, it was pointed out on that post that only the set variable script step shows the limitation, meaning that a variable set with a Let() function can set the variable with the repetition as desired. Let ( $$LONG_REPETITION[9999999999999999999999999999999999999999999999999] = 10; 1 ) I think that make the most sense for my fix. That way I only have to adjust everywhere the variables are being set and where they are being referenced can remain the same. I haven't tested it myself yet, but will tomorrow..
  13. FM 16 Variable Repetition limitation change?

    So here is the issue simplified which had nothing to do with code ( Get ( windowName ) ) after all. Variable repetitions in FM16 appear to be limited to 18 digits. If more than 18 digits are entered it will use the last 18 digits of the entered string whereas FM 15 and prior did not have this limitation. This throws a big monkey wrench into my works as I use the technique of "Bucket Variables" as I now recall it being called in several techniques that I've developed and use on a regular basis. Not only do I use code ( Get ( WindowName ) ) but I also use Code ( record::ID ) in many places to set a variable to an individual record. Ugh! Now to start checking through my solutions to find where this is going to bite me. I would certainly welcome any suggestions for a work around for unique repetitions since I'm loving the new features of FM 16 but have to adjust all my files to be able to use it...
  14. FM 16 Variable Repetition limitation change?

    As a follow up. I set a variable $window to Code ( Get ( WindowName ) ) and then entered $window as the variable repetition. The value of $window shows as 11600115001010008400101001000011100099 but putting $window in the variable repetition shows as 101001000011100099 And as I'm entering this post I just realized that the perameter shows as the last 18 digits of what the value in $window Well, that seems to be it. The Variable parameter seems to be limited to 18 digits and it uses the last 18. I entered 11600120001010011600032001140010100103001100011100108000320011600115001010008400101001000011100099 as the variable repetition and the result was 101001000011100099 as the repetition Is this expected behavior?
  15. I have been using a navigation technique I developed back in FM12 and have used successfully in 12, 14 and 15 that utilizes global variables to track forward and back history. In order to make it multi window friendly I use Code ( Get ( WindowName ) ) as the variable's repetition number. When I updated to FM16 the navigation script failed. While investigating the failure I found that Code ( Get ( WindowName ) ) as a variable repetition in FM 16 resolves different than it does in FM 15. I created a test file and a script that set two variables as shown below. The name of the window is codeTest Here are the results in the Data Viewer of both FM15 and FM16 As we can see the Variable repetition result is different in FM16 for code ( Get ( WindowName ) ) and different than the result in the variable value... I am on Windows 10 I've tested on both local and hosted files with the same result. ( Unfortunately this was not the actual failure I was looking for. In the script in question the global variables do not get created at all in FM16 which appears to be a different issue. Still investigating.. ) Can anyone confirm this? Or has there been any other strange behavior when setting variables reported? Also, now what? Thanks Ron codeTest.zip
×

Important Information

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