Jump to content

Racer Bob

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Racer Bob

  • Rank
  1. USB Stick protection. I tried using the USBSentry system for protecting my files to end users. However I would caution anyone from using their system. They never provided me with a working system and refused to refund my payment. Instead I was forever locked into their PlugIn operating in the Demo mode which was unacceptable. Addendum : After several email exchanges I was given the proper registration codes. The instructions were somewhat confusing and they promised to make them clearer in the future. So far it all works as intended. I had also looked into the 24
  2. Is it necessary to have the runtime file in the same folder as the data file(s). This is an issue with Vista. As I understand it, the runtime should be placed in the programs folder. If the data files are in another folder (documents etc) will clicking on them launch the runtime. And then again, will launching the runtime automatically open the data files from their folders. Bob M
  3. Your right. Because the normal way to specify the Layout name in the script step is to choose from a list, it is automatic. If one usee the calculation method and hand entered the layout name without the padded end space, it won't go to the layout.
  4. Sorry, since you didn't say anything about an extra space padded onto the end of the layout name I had to figure it out myself. It only shows up when clicking on the layout name in the layout setup box. Then the whole name is highlighted and it is possible to realize there is extra space on the end of the layout name. Clearly the IF statement is much more "literal" than the Go To Layout step. That is what was confusing, being able to call up the layout by the padded name but not process it in the IF statement. All works out in the end. Thanks for the reply
  5. Thanks for the replies. What I have found out is that it had to do with that specific layout Name. THE ANSWER When naming the Layout, a blank space was attached to the end of the name. Of course this isn't apparent in the Layout Setup form. This came about because the new layout started as a duplicate of an existing layout. While changing the name, the space ended up at the end. Padding clearly is possible with Layout names. While this didn't cause a problem with the script step to display the layout, the IF statement was another matter. It took into account the extra bl
  6. Let me make it clearer. Running Debug and the Data Viewer clearly show the correct name of the layout is being obtained by the Get(layoutName) function. But the simple IF statement won't act on it. The step is IF (Get(Layoutname)="Parts Invoice Layout" The Data Viewer returns Get(Layoutname)="Parts Invoice Layout" Yet the IF statement skips the following script step and goes to the Else condition. I have run into things that refuse to work before with FileMaker and usually requires deleting the entire problem issue and re-constructing it then they work. No chan
  7. Thanks, Facing a learning experience with runtime applications distribution issues, especially Vista. Bob
  8. I have encountered what seems to be an inexplainable failure of the IF statement. Case I have a script I want to have act differently depending on which Layout is displayed. However, the IF Get(LayoutName)= "xxx" refused to evaluate. I know the Layout name is valid as that is how it got displayed. But the IF statement will not evaluate as true even though the Date Viewer shows the correct value for the Get(layoutName). I can make it work by which window is displayed, but not by the Layout displayed. This seems to be a little strange. I have tried deleting the statement and
  9. Could you explain how to "unlock" the file. I am not sure what this means. Thanks bob
  10. This really has me stumped. Almost to the point of dumping FM. I have a parent table and two related tables. Each table is set to allow the deletion of the related records when the parent record is deleted. It is not allowed to delete the parent record if the related records are deleted. But FM has it's own mind. One related table works as it should. The other will delete the parent record when a related record is delete. It does't matter if the related record is deleted by script or hand, nor from which layout. I have deleted the relationship and started over but nothing c
  11. Need someone's experience here. I am trying to use a very simple application of a second window. By script, a small window will open from a button to display a reference table. The problem is when the second window opens, the overall size of the original window (width and height) is reduced about 10% and stays that way even after the smaller window is closed. What is this all about ? very annoying. Also is there any way to lock the over all size of the second window, not allowing users to expand it or minimize it. ?
  12. Well, since there is an arrow pointing left to the button and I can enter a number into it, I think I have a button that the tab function accepts as real. What I have discovered is if I put a button in the body of the list view, as if it was another field, it will work, although only by using the "ENTER" key on the number pad, nothing else will activate it. However, the original button, which is placed in the Header area of the layout along with field titles, will not be tabbed into, even though it has an arrow and has the correct sequence number. Problem it that since the working bu
  13. While the user manual is a little thin on this subject, other info says that I can set a tab order to include a button on the layout. I have followd the instructions, selected "objects" and numbered the fields so the next tab numbered after the last field is a button. Problem is , it won't go to the button, it just skips back to the first field in an endless loop. I tried removing all tabs and starting over rather than renumbering and deleting existing tabs but it doesn't make any difference so I am stumped. Anyone have this problem besides me.
  14. This is an interesting item. On my Compaq desktop the "RETURN" key, the one in the main key area is called "ENTER" and will not activate the "Enter" key function in FileMaker. However the "ENTER" key for the number pad does do what the program wants. Also, does anyone know exactly how the use of the "ENTER" key to end data entry and commit records is effected by selecting the option for Field Control to allow using either the "Enter" or "Return" keys to move from field to field. Does this overide using the "ENTER" key to commit records or end the data entry proceedure.
  15. Subsequent Investigation Shows the following information which should help anyone else encountering this situation. When a new record is entered through a script using the NEW RECORD REQUEST, there is no way to keep the script from executing all it's included steps before the program will go to a field and start taking entry of values for that field. If there are any steps that must not be executed until after the values for the new record fields have been entered, they must not be included in the same script that contains the NEW RECORD REQUEST. This also applies to a sc
  • Create New...

Important Information

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