Jump to content

Mark Hardee

Members
  • Posts

    28
  • Joined

  • Last visited

Mark Hardee's Achievements

Explorer

Explorer (4/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. Generally construct value lists from field values.. That way you are only display unique values.. So, yes, you are the only one! :-)
  2. Seems as if I remember a unique way that JavaScript must see a UNC... something to the effect that the UNC must start with 2 "\\" as the first one is an escape character? Might be worth a shot?
  3. You will have to scan data to see if it follows a pattern. Read up on Middle and Position functions... Or just get AHunter3 to do it for you! He is a zen master!
  4. I just installed a runtime created on FM10 Adv on a VISTA 32 bit machine onto a Windows 7 Home Premium 64 bit box and it seems to be working *except* some relative paths I had in scripts evidently... Trying to look into that right now.... Geez.... why doesn't everyone use Macs?
  5. Oh, I get her meaning now... But, the workflow in this scenario is after the records are exported we are now done with this data. A backup of the Filemaker file is made, ALL records are deleted and the new day's data is imported.. Each day is a , well, a new day! I see that if we were to want to keep all of the data, we could set a record as exported and then loop through only those records that did not have that flag set.. thus not adding already exported data to the "newly added" data for that day.. Mark
  6. Yes, I am exporting all of the records although they are exported to multiple files differentiated by the store number. As I see it, it gives the opportunity to perform the loop.. while we are finding data by looping through and changing the counter values, exports are done. Once it get's to the end of the "Stores" list (no more valuelist entries) it will find "0" records and give the script a way to proceed to the Endif... As I stated, it works like a MURF! I will try the other method as well... one can never have too many ways to accomplish a given task! THANKS to all that replied.. I hope one of these days I can attain the knowledge to help out...
  7. Avoiding export the record twice by this section: Set Variable [ $Stores; Value:ValueListItems ( Get ( FileName ) ; "STORES" ) ] Go to Layout [ “IMPORT” (IMPORT) ] Show All Records Set Variable [ $Total; Value:ValueCount ( $Stores ) ] Loop Exit Loop If [ Let ( $Counter = $Counter + 1 ; $Counter > $Total ) ] #Find all stores for current loop ... Enter Find Mode [ ] Set Field [ IMPORT::STORE; GetValue ( $Stores ; $Counter ) ] Set Error Capture [ On ] Perform Find [ ] Set Error Capture [ Off ] #If we found records for this store, lets export them now... If [ Get ( FoundCount ) > 0 ] Getting the unique value of store "name" by using a valuelist, counting it, performing a find on the first value, exporting it and moving down the list and looping the find and export. When the value list has been looped to the end, all data has been accounted for and exported... Why go to excel? That's what the client wishes and the exported data will then be imported into a variable data print application. I've done the VDP stuff for years and the basis for a successful workflow is feeding it clean, precise data... that's where Filemaker comes in.. Reports are still generated in Filemaker for analysis, job tickets, workflow verification and checklists.. This whole deal (Value Lists) opens up a whole world of possibilities for segregating data and knowing that you have all and only the data you are seeking as the value list contains ONLY unique values..
  8. Thanks... with the help of a saviour, Weetbix, who has pulled my can out of the fire more than once, I got it figured out.. Valuelist... Ended up with: Set Variable [ $Stores; Value:ValueListItems ( Get ( FileName ) ; "STORES" ) ] Go to Layout [ “IMPORT” (IMPORT) ] Show All Records Set Variable [ $Total; Value:ValueCount ( $Stores ) ] Loop Exit Loop If [ Let ( $Counter = $Counter + 1 ; $Counter > $Total ) ] #Find all stores for current loop ... Enter Find Mode [ ] Set Field [ IMPORT::STORE; GetValue ( $Stores ; $Counter ) ] Set Error Capture [ On ] Perform Find [ ] Set Error Capture [ Off ] #If we found records for this store, lets export them now... If [ Get ( FoundCount ) > 0 ] Set Variable [ $export; Value:"file:EXPORTS/STORE_" & IMPORT::STORE &"_"& Year(Get(CurrentDate)) &"_"& Right("0" & Month(Get(CurrentDate)); 2) & Right("0" & Day(Get(CurrentDate)); 2) & "_" & Right("0" & Hour(Get(CurrentTime)); 2) & Right("0" & Minute(Get(CurrentTime)); 2) & ".xlsx" ] Export Records [ File Name: “$export”; Use field names as column names; Author: " "; Character Set: “Unicode (UTF-16)”; Field Order: FIELDNAMES OMMITED ] [ No dialog; Format output using current layout ] End If End Loop
  9. Not at the moment, but, I wish I had the data for that.. Currently it is in the flat data that is client supplied, and you KNOW they know what they are doing, right? :-) After reading my post it wasn't very clear... for example: 20,000 records - a field labeled STORE which contain the store number. ( Possibility of 300 - 400 stores - but not every one places orders each day) Of that 5,000 are for STORE 1, 1700 are for STORE 3, and so on. The number of stores varies with each data import and export scenario.. daily... So, let's say Monday we import 10K records, where the STORE field is populated with "orders" for one of any 200 stores. What I need to accomplish is to export the data for EACH store to an Excel file for further processing (variable data print job)... So, either manually find and export data for each of the 200 possibilities or be able to evaluate the content of the STORE field, select matching records, export, perform find for next store, export, and so on until all data has been exported. So if "today's" data had 26 stores with orders that happened to have 100 records for each store, I would end up with 26 excel files and each excel file would contain 100 records.. The equivalent of: FOR STORE = 1 DO WHILE STORE = 1 EXPORT NEXT STORE
  10. I am approaching the end of a project and have run accross a (to me) barrier. FM 10 ADV... Couple hundred thousand records. There is a field that identifies the particular store. There are hundreds of stores each with thousands of records.. I have exports working as needed. What I need to do is: Select from all of the records STORE 1 Export its records to a file Loop through the entire database and select records by EACH store number and export ITS data... I will never know which stores are in the current group of data...... Any ideas? I appreciate any help or direction anyone can point me in....
  11. Thanks for the info.. Just wish it was as easy in Windows to do what is so easy via Applescript... Portland, eh? Spent a couple of weeks in Medford.. I love your part of the country.. Took the jetboat river ride to Hell Canyon (I think!)..
  12. If I do use the Troi plugin, what happens when I create the runtime?
  13. I have a solution that I made several years ago to manage (mangle) gobs of data from hundreds of sources for a Print On Demand Solution.. I've got a LOT of work in this.. I have a new client that I can taylor this application to his needs and not have to do literally months of work on. There's one minor snafu.... The one I developed is on the Mac platform. A very important part of it is a script that uses an Applescript to import a WAD of files in one session and do various nasty things to the data during import. Of course this client wants to run it on a Window 7 box.. I plan on providing a runtime solution.. The (borrowed) script I have used (with some minor folder name changes is: set theFolder to choose folder tell application "Finder" set theFiles to (files of theFolder whose name extension is "xls") as alias list set old_delims to AppleScript's text item delimiters set AppleScript's text item delimiters to ASCII character 13 set theFiles to theFiles as Unicode text set AppleScript's text item delimiters to old_delims return theFiles end tell The $64K question is how do I use the portion of the script that uses Applescript on a Windows box? Is there a magical Applescript to VB application? Thanks, again for any help....
  14. Hello all.. I swear I have done this before, but, am filed with Brainfade at the moment. Filemaker 10 Adv. Working on a solution to produce data for shelf talkers for a client. Data import issues have been resolved and would definitely like to add a very important field to each file that is imported. Hundreds of files to import each time with filenames like "Signs_00001_725351.txt". These are pipe delimited and have done all of the calculations to import the data into the correct field. Each file may contain 100 - 200 records and there are proposed to be 700 or so files each time. What I would LOVE to have happen is during import, could I grab a portion of the filename of the current external file being imported and either: Have it imported into all of the current found set (during importing) or at the very least put it into the first (or last) field and script the copying of the data from the populated field to the rest of the remaining records for that import? Evidently, the identifier for either the store or type of shelf talker exists only in the filename itself.. Thanks for any directions anyone can offer... Update: I found a solution to do this: http://fmforums.com/forum/topic/65562-create-batch-import-script/page__view__findpost__p__310812 THANK YOU Post Master General!!!
  15. This looks fairly simple.. Your page setup size is 4 x 2.31. Your Filemaker "page" is the same. There is no way it will ever put the layout more than 1 up.. Looking at your print setup, it appears as if you are trying to print to a label printer. The repeat of the label will have to be your page size.. period. If you are trying to print multiple records up on 1 label, you have another whole set of issues...
×
×
  • Create New...

Important Information

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