Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mgeorge

  • Rank
  • Birthday 03/29/1960
  1. Just go to http://sislands.com/coin70/week6/encoder.htm for an explanation of the process.
  2. This is what it translates to: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head><SCRIPT LANGUAGE="JavaScript"><!-- <META HTTP-EQUIV="Pragma" CONTENT="No-Cache"><META NAME="Robots" CONTENT="NoIndex"> <title>BLANK</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <link href="/CSS/FM.css" rel="stylesheet" type="text/css"> //--></SCRIPT></head> <body><noscript>To display this page you need a browser w
  3. I created a help script that checked the name of the current button script when a modifier key was held down and then displayed an appropriate message. This could also be adapted to place the help definition in a status field as well. Set Error Capture [ Off ] Freeze Window If [ g_cur_scriptname = "" ] Show Message [ Buttons:
  4. TechInfo article no. 104081 at www.filemaker.com states the following: "When a file opens due to a relationship (i.e. a related field appears on the current layout) ,an external script, or a value list that uses a secondary file, the startup script for the related file will not run. To compensate you will need to anticipate when files will need to be opened and open them with the Open script command." Mike
  5. I'm sorry, I think I left out an important piece. I don't open the secondary files from the central database using an 'open[]' command. I force them open by executing a subscript from each secondary file. When it is done this way the startup script for each file is not run. Secondary files startup script: Toggle Window[Hide] Open[Open Hidden, "centraldb.fp5 (gov.ns.ca)"] close[] Primary file startup script: Perform Script [sub-scripts, External: "Acc.fp5 (gov.ns.ca)"] Perform Script [sub-scripts, External: "Att.fp5 (gov.ns.ca)"] Perform Script [sub-scripts, Externa
  6. I used to get upset with users when they constantly did things 'wrong'. It was only 'wrong' because I hadn't thought that anybody would do that. Therefore I was 'wrong' in not anticipating the users interaction with the database. Then I realised that the only way I would keep my sanity is if I controlled every single step they took. I mean validation on almost every field they could possibly enter data in, creating separate 'browse', 'edit' and 'find/search' layouts, keep track of where they are in the databases at all times, trap all errors, singular entry/rentry points. Fully half of the ca
  7. I had the same problem until I realised the best method for me was to have all the secondary files run a startup script: Toggle Window[Hide] Open[Open Hidden, "centraldb.fp5 (gov.ns.ca)"] close[] Once centraldb.fp5 opened it would execute a startup script that took care of setting years, window cleanup, and then user routing. The user routing routine would then selectively open secondary databases depending on the user log in and execute the setup subscripts for those individual databases. The short answer is basically all roads lead to Rome and from there the world.
  8. One issue that i've run into, is that if a validation calculation is attached to the userdata fields being audited, is that the trigger gets set twice resulting in a double entry in the audit history. Just add a validation to userdata1 and userdata2 and see what happens. Mike
  9. Your right about the globals. That's what I get for not reading your original reply correctly. Mike
  10. I had a similar problem with one of my FileMaker Server projects - about 6 users would from time to time enter data in Find mode thinking they were in Browse mode. I fixed the problem by creating a find/search layout similar in structure to the edit/browse layout. They could only do a find by selecting a button that called a script to this page. When the search concluded it would take them back to the edit/browse layout. Each layout displayed a banner indicated which mode they were in. Mike PS. I don't think the globals will work in a server based solution.
  11. I had a smilar problem in FM 5.5 under OSX. It turned out the the PS font used in the layout was an old one and the printer component of the font wasn't being sent to the LaserWriter. Changed the typeface - converted it to TrueType - and the problem went away. Other postscript fonts printed just fine. Mike
  • Create New...

Important Information

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