Tip 2: If you are going to start to tie down the database by requiring security log on, think about adding TWO ways into that database. I like SplashID but there are a lot of similar products, some free. If you have a Windows machine, you might consider looking for some software that will guard important pin numbers, log on, account info, etc. I recommend that you put that logon into the Keychain if you have a Mac computer. You must remember that Admin is the default. It will probably default to your user name, you use to log into your computer. But when Filemaker Pro crashes it might start asking for a logon. Unless you set a password, you should be able to get in without using any logon. Tip: Before you put in hours of time building a database, add one or more full access users to that database and record the logon some place that you will not forget. Put that user name and password (blank) into your computer Keychain application so you will remember.
Enter “Admin” for the user name and leave the password blank. It took quite some time but the trick is this. When I restarted the program and went into my database, that I had been working on, the progam now asked for user name and password. I was creating envelope template when the program crashed. But the default field name is hardcoded, so beware of changing that in Manage > Database if you use this generic find approach.After spending about a week putting together a significant database I ran into a glitch that astounded me. The part above like GetValue ( Substitute ( GetFieldName ( Invoices::invDate ) "::" ¶ ) 1 ) is a good way to avoid hardcoding table/field names in your script, which will protect your script from table/field name changes.
If the name of the field is different, you might have to add some additional branching logic. TableName::dateField then a script like this could work: Enter Find Mode If the name of the field is the same in all the tables (e.g.
0 kommentar(er)
