Jump to content

haensz

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About haensz

  • Rank
    member

Profile Information

  • Gender
    Male
  • Location
    Columbus, OH

Contact Methods

  • Website URL
    http://www.archivedata.com
  1. Dansmith65 -- My typical use for ErrorCapture is to handle find requests. If a user attempts a search that brings up no found records, I prefer to literally show them an empty list rather than loop them back into another search attempt. Seems odd I know, but a lot of my users were getting frustrated when search attempts would "stick them in an endless loop"... Anyone here in the forum would know that if they'd quit messing up their search request in the first place then it would be able to retrieve some records for them !!! But it's probably just something I was taught to use ear
  2. That's a great video. Holy cow! I did not now that reverting the parent record also reverts the portal records you were about to modify as well. Embarrassing, but maybe that's why you're actually supposed to read some of those manuals instead of just diving in, huh?
  3. Obbe -- sorry I disappeared on you for a while. Sounds like you have your issue in hand. But for future reference, I wanted to get back to you on your question on Scripted Imports. Just remember that the import will bring in all records from the source table's current found set. So prior to your scripted import, make sure that you've scripted that source layout to display only the records you want to import. A few ways to handle this, basic way would be to: 1. Set Error Capture ON *** Very important step here! *** 2. Go to desired layout 3. Perform Find 4 Go to Layout (origina
  4. I agree. Sounds like you can use the one "Students" table and add a few new fields: Status (values would be HS Student, Alumni, Other Univ Student, etc) HS_GradYear (would only need populated if Students::Status field = HS Student) This will let you filter or sort easily based on the Students::Status field. And you'll be able to handle the issue of which HS Students to start contacting as they enter their Senior year. If you are worried about the table growing too large because of the # of HS students each year that enroll elsewhere: 1 -- Don't worry, FM 11 can handle
  5. LaRetta -- could you send me a sample of what you're talking about? At least enough so that I can get on the right track and Google to learn more. I've used batch files occasionally as a work-around for random issue like this, but I've no clue what I'm really doing when writing them!
  6. Do you store the Offer ID (or whatever your primary field on offers table is) on the Invoice? If so, you could create the new invoice record and tag it with it's Offer ID (store this Offer ID as a variable $offer). Now you have a relationship to pull the customer #, address, date, payment info, etc -- all of the basic info I'm assuming that your offer record would contain. Then go to the table you mentioned that links the line items/products from your Offer ID. It sounded like this table was unique based on the Offer ID and the Product/Line Item. Perform a find based on the $offer
  7. Similar item for my wish list would be to know if a related record is in use. Basic example -- you've got two tables: order and order_lines. A sales rep is changing something on the line item of an order (so they're locking up a record in order_lines). I don't want another use to try to process that record on the order table -- even though that order record is not in use, it's line items are being changed which could result in a mess for me to clean up...
  8. I have a couple spots where there are issues like this but it IS important to know who's in there. Let's say the process of invoicing customers. For unrelated reasons, we can only allow one person to invoice at a time. I first take them to a bogus table, with one record with fields like "Invoicing_InUse" and "Invoicing_User", and set the fields to "1" and "Jane Doe" respectively as the user begins the invoicing process. Then whatever the last button or script in the invoicing process is, I would clear out those Bogus::Invoicing_InUse and Bogus::Invoicing_User fields. That way if a
  9. Is this the only FM6 file that these two users access? One of the users could be inheriting unwanted permissions from a different file if it also has a group named "Administration" (with the same blank password). Vaughan's advice above is ideal, but not always practical. No sense in trashing your FM6 files if they're still chugging along without too many issues. I'm somewhat embarrassed to admit it, but I've got plenty of FM6 dinosaurs plugging along in my production environment still...
  10. Does your export contain related records? I've had this issue when one or more of the fields in my export was from related table. If they are multiple related records then it will create rows in your export for each.
  11. In the "Under the Hood" session at Devcon this year, we learned some great info on exactly what is happening behind the scenes as your FM clients navigate through the layouts & records you've prepared for them. It was a very useful session EXCEPT that up front they said that almost none of this applies if you are using ESS. It only pertained to the payloads moving between server and client for native FM tables. Does anybody know where you can learn some in-depth specifics about the speed/performance of displaying or manipulating ESS tables? I'm using ESS extensively in one of
  12. Does anyone know how to grab the create date and time of a local file? I'm pulling vendor catalog feeds into FM11. Up until now I've just been inserting the current date & time as the catalog date of the newly imported file -- the assumption here was that if a new catalog file was delivered to our FTP folder, then it was actually NEW! Worked fine until I discovered that one vendor has been sending an old catalog every morning. So I've been processing the same file needlessly every day... Just in case I've missed a external function that's already under my nose -- I have SM
×
×
  • Create New...

Important Information

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