Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bdavid

  • Rank
  1. I like the idea of a user table - it will make my life easier going forward. Thanks. The field using Get(UserName) is set up as a calc field with a text result (Auto-enter/don't replace existing value, if any) to capture the user name once at record creation. The user can't enter the field in Browse mode. I thought this was a good way to do this....suggestions? I guess I don't understand about not being able to migrate the passwords - they must be stored somewhere in a hash table, but I guess that's not exposed to us mere mortals. Maybe in the future I will need to move to LDAP avoid
  2. Barbara - thanks for the tips! FYI - I used Get(UserName) since I merge this field in a few internal reports, and wanted their full name from their prefs. Maybe I'll re-think this.. Regarding the import, I already imported without the auto-entered option, but the field in the target DB re-calculated using my local UserName. Maybe I am doing something wrong, so I'll go back and check again. I have worked around this by changing the target field to text, getting the data in, and then changing it back to the calc. On a related note, how would I move over the account info from the sourc
  3. Hi all - Simple question from a newbie (I hope). I am in the process of importing data from an existing database and one of the fields I use to track who entered the data for the record is automatically populated as a calculated value from Get(UserName). How do I prevent this from re-calculating and using my user name for all the records? Thanks
  4. Cool idea about the scheduling the script on the server. I have deployed on FM server, so I'll go that route. Thanks again for the help!
  5. Thanks for the response Mr. V! Yep - I kinda figured I would need something like what you are suggesting. Turns out I already have a script that spits out a pretty report for this condition, so I guess could use the "guts" of that to pull out the records I need into the email. At the risk of revealing my infinitely small knowledge of FM, how do I set up this script to run automatically each day to check the records and send the email? A script trigger that gets fired when anyone logs in for the day, set a flag that it's been run for the day, and then prevent all other logins from ru
  6. I would like to set up a trigger of sorts to send an email for any record in the database that is based on an upcoming event date where the event date is less than 2 weeks away from a stored target completion date. I understand the logic needed (I have conditional formatting set up already to visually highlight the date), but is there a simple way to do this per record check (aside from looping through all the records to check this condition)? Hope I explained this OK.... Thanks -
  7. Well chalk one up for a newbie - I had a leftover script trigger on the fields and IWP does not like this. Removing the triggers did the trick and I can now edit the fields thru IWP. Hope this helps someone avoid this issue -
  8. I have an existing FM10 DB and I have put together a new layout that I want a web user to run reports from. The layout works fine in FileMaker, but when published through IWP it does not allow you to enter any fields though a mouse click. If I go to the IWP status area and click "Edit Record", the fields become "enterable" and my scripts can use this data and work fine. My question: Is this expected behavior or have I forgotten to do something when launching this layout? I should add that my goal is to not use the IWP status area (Hide/Lock) and the only thing keeping me from accompl
  9. Ah - the light went on this time! I'll give this a shot and report back. Thanks for putting up with a newbie.
  10. I already have this relationship set up but it is the "matching" that I am struggling with. My table relationship is: Deed List -> Used Deeds where the deed list has a record for each state, and four possible deed_types in each state. I need to choose the proper template for the deed type, but can't figure out how to do the matching without a case statement or something similar. I know I am missing something in my approach - sorry for the simple minded questions...
  11. Hope I explain this correctly.... I am putting together a real estate application and I have a set of deed templates in containers in a table that I want to choose from based on two conditions: - State - Deed Template Type (A, B, C, D) I have a dropdown list on one layout where I have fields that I want to merge and a value list with template types to choose from. I am having trouble figuring out how I set up a calculation to choose the proper template type from the table with the containers that hold the templates and return the file name into a new field so I perform the m
  12. Excuse the newbie question, but I'm stuck and need some guidance: I have a fill-in layout that shows a series of checkbox value lists in this manner: [ ]STUFF 1 [X]STUFF 2 [ ]Stuff 2 subvalue A [X]Stuff 2 subvalue B [X]Stuff 2 subvalue C [ ]STUFF 3 [ ]Stuff 3 subvalue A [ ]Stuff 3 subvalue B [ ]Stuff 3 subvalue C I need to generate a report with all of this information in a special format and I am trying to understand how I can test to see which value list items have been checked so I can indicate this on the report. I can't just show the value lis
  13. Working on my first FMP project : and I want to create a dropdown list that will only show the appropriate choices for companies in a given state. The state is part of a table of people that you will search for by name, address, reference #, etc. I want to filter the dropdown list to only show companies that operate in the state where the people are. What is the most efficient way to do the filtering? Should I just populate another table by triggering a script that will do the appropriate find and then populate the value list from there? New to this ...thanks in advance for your advi
  • Create New...

Important Information

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