Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

RDWirr's Achievements


Contributor (5/14)

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

Recent Badges



  1. Super! Many thanks Comment. This is exactly what I need to get rolling with a solution.
  2. Aha! That broadens my view considerably. I need to play with this a bit to decide which is the better route whether keeping everything in the range structure or enumerating the ranges and storing it all as single numbers. In the mean time, could you give me a hint on how to or where to find the way to enumerate a range with a script? I have found a couple custom functions on line but no scrip examples. Thanks very much Comment for your help with this.
  3. Thanks for the good information Comment. Yes, there were two questions. The important one is how to convert what I have now. I think my data is relatively clean in terms of consistently entered. but probably some cleaning is well advised. As you can already notice, I am not so skillful with scripts, but always willing to give it a go. I have a couple questions though: I assume this is a multi-stage operation that you suggest. First separate everything that is a single number/word and create records for each of these, deleting them from the original data, before going on to substituting the hyphens for spaces in the case of ranges. Otherwise the single numbers and ranges cannot be discriminated. I will have to muddle through this but my first puzzle is how to determine if the word between the commas/spaces is a single number or a range. They can have variable numbers of digits. How to create a list of records from the RangeStart and RangeEnd fields? In my newbie way of seeing things, it seems like I would have to move each separate range to a field, substitute the hyphen and then perform the creation of the list of records within the range, then loop back to take the next range in the record and repeat. The second question is something we have to do some human engineering on. The users are customers and spread over a wide geographic range, training could pose a challenge. We actually have the list of all possible serial numbers that we give each customer so asking them to check them off as they use them is good from a data standpoint because it gives us a more robust auditing dataset and probably less prone to entry errors, but getting them to click through a long list of single numbers would for sure cause some complaints. Maybe the best place to look is how accounting systems handle serialized item invoicing and stock movements. Anyway, your suggestion to use a related table with each serial number enumerated is a very good one. Just a matter of how we manage implementation.
  4. I guess the next logical question would be, how to convert this mix of data to a related table? All the records with a single serial number are straight forward but how to parse the records with multiple comma separated numbers, each with the accompanying 'no_shipment' match field? But more importantly, how to list out the ranges? I have searched around and haven't found any techniques that clearly describe how to convert a range (,123-125,) to a list. I have many thousand of records in this table that have mixed data and converting it all manually seems like a daunting task.
  5. Thanks for the input Comment. I was afraid of this. So no way to find anything that looks like a range, convert it to a pair of numbers and then do a calculation? The problem we have is that this information is entered manually by users who are shipping items with these specific serial numbers (wins). I suppose we will have to build a system to give the user a list of possible serial numbers to select but that could get a bit cumbersome, clicking through 100's of numbers. Any ideas on possible ways to manage this would be much appreciated.
  6. Hi Lee, Thanks for the guidance. I have a table with some records, in each record is a field that has this mixture of ranges and single, non-sequential numbers. The content in this field varies from record to record, some can be just a single number, some can be a contiguous range i.e. 12345-12350. But often there are a mix of both contiguous ranges and non-sequential single numbers i.e. 12345-12350,12360,12362...etc. The numbers to find can vary in length from a single digit to the millions. I need to find the record which, in that field, my find criteria matches either by a direct match with a single non-sequential number or within the range of the range type numbers, i.e. 12347 is found in the record that has the data in the field I am finding in "12345-12350,12360,12362". I have attached here some examples of the numbers in the field I want to search. To reiterate, I am trying to find the record that my search criteria matched in the wins_used field you see in the attachments. Basically the application is to find which shipment a particular serial number (win) was in. My operation is to put the Find criteria in the FindShipment field, you see in the image, then trigger a script to search through the wins_used field in all the records. I am sure there is a way to do this but it is as yet beyond my skill level.
  7. Building on this last solution, I realize I have another more complicated problem. I am trying to perform a find on records which have a single field that must be parsed into multiple criteria. I am trying to finding a single record that has a field that contains data like this "295621-295640,295642-295660,295662,295670,....". Find criteria would be for example 295645, always a single number. I think I need to step through the data in each record, parse the start and end numbers of the ranges with the hyphen perform a find and then start a new find range with a comma. If there is no hyphen, then it is a non-sequential number that still has to be detected and searched. Some of the records can have 100's of these mixed sequences in them. The current database has around 30,000 records in this table and growing quickly so the time to step through all this to find where a number fits could become problematic but that is a secondary concern. If it takes a minute or two to perform the find, no big problem. I am unclear if I should be making a new post for this but since we were on the subject, I thought it best to just carry on. Thanks in advance, RDW
  8. Thanks Comment, that works perfectly. To answer your question, yes, the find criteria is a single number. I was fumbling with this at first because of getting strange find results but then realized that my start and end numbers were formatted as text in the table. Once changed to numbers, it works perfectly. I guess I need to brush up my scripting skills.
  9. I am running FileMaker 14 on a Win 10 machine. I have a set of records that each have a field with a starting number and a field with an ending number. I have to perform a find that locates the record where the find criteria is greater than or equal to the starting number AND less than or equal to the ending number. I need to write a script that will just let the user enter the find criteria in a edit box and then go to the record. This will theoretically be only one record that would match from the dataset. Can anyone point me in the right direction with this? Thanks RDW
  10. Hello Comment, Thanks for that. Worked perfectly. I guess I was trying to make things more complicated then they needed to be. Thx, RDW
  11. Hi Vaughan, I found it. I had the menus set to minimum. It needs the available menu commands set to all. Thanks for the help, RDW
  12. I have some records displayed in a portal each with a button to go to the record on a different layout that is based on a non-related TO. So it's not a GTRR since it's not going to record on a related TO. I am actually going to a record in the same underlying table but just jumping from one layout to a different one that is based on a non-related TO. My Relationship Graph is getting pretty spidery as it is and I am trying to keep to the anchor buoy method as much as possible. I have tried setting a variable with the original recordID and then go to another layout with a record that is related to the destination TO and doing a GTRR from there but it isn't working for some reason. Anyone have a standard approach to such a thing? Thx, RDW
  13. Hello IdealData, Thanks for the tip. That worked. Playing with it a bit more, I noticed that the width doesn't fully follow the width of widest record. I did what you said and it provided enough width for my purpose but I noticed it seems to average the width of the less wide records also...or some such logic. If I put a lot of spaces in there, it doesn't get any wider, it just shows some ellipsis at the end of the dummy record in the drop down. Would be nice if they allowed us to discretely modify the width. I'll have to figure out a way to automatically put this dummy record at the top of each drop down. I have a lot of dependent conditional VLs that will need a dummy record for each combination of conditions. Thanks very much for your help. RDW
  14. Hi Comment and BCooney, Thanks for your help. That was indeed the problem. Once I allowed the "hiliteSortedBy" field to be modifiable, it worked. I wonder if I could ask another question while we are on the subject of security. What is it in the privilege setup that controls whether an account can go into Preview Mode or not? I have one privilege set that allows pretty much full access to everything except modifying layouts and some housekeeping fields and I have allowed printing but for some reason the preview and all of the buttons except navigation on the status bar are grayed out. Thanks again, RDW
  15. Can anyone tell me how to control the width of a drop down list? I have a DD list that drops down from a semi hidden field (1px wide) that always truncates anything more than 7-8 letters long. I'd like to find a way to control the width of the list so it could display something like 20 characters. Anyone know how to do this in FM10Adv?
  • Create New...

Important Information

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