Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

SlimJim's Achievements


Proficient (10/14)

  • First Post
  • Collaborator
  • Posting Machine Rare
  • Conversation Starter
  • Week One Done

Recent Badges



  1. Regarding loss of index - I don't know how easy it is but I think this is the first time this has happened to me and I have been using Filemker since Version 2.1. However, 'using' may be the key. I generally make databases for my own use and once they are up and running I only make changes when I want to change the structure. In this case the database was for business use, the company split into two parts and needed to have separate invoice numbering for each of the two parts. So I added a new field to identify which company was issuing the invoice and a new auto-enter based on an additional relationship to determine the invoice number after the company field was populated. I am now certain that this is what caused the problem with indexes. Invoices issued after this change could be found the ones before couldn't.
  2. Missed your post while replying to Inky Phil. I have actually just done the v3 update. I have been thinking back and the only change I can recall making was a modification of the auto-enter calculation on InvoiceNumber and it rather looks as if that was the culprit. Many thanks to both you and Phil for responding so quickly.
  3. No I haven't and that is what was required. Many thanks Phil
  4. A problem which has started in the last week or two. I can no longer find invoices by number. My Invoice numbers are serial numbers, (of number type) starting at 1. When I input a particular number, which I know exists I get back no records. If I put in the find "> 0" which should find all the invoices it only finds the ones in the last two weeks roughly. My first thought was that somehow the numbers had been changed to text so I put in an extra field defined as a calculation GetAsNumber(InvoiceNumber) and then when it had calculated converted it back to a number field. Fnding using this field works as normal. The next step was to replace all the InvoiceNumbers by the numbers in this new field, this made no difference to the finding problem! I checked the validity of the InvoiceNumber field using a script looping through all the records, again no problem. They are all numbers but they still cannot be found. I want to avoid replacing the InvoiceNumber field by the new field as InvoiceNumber is used in numerous places, in relationships, scripts, calculation fields and auto-enters. Can anybody shed any light on this?
  5. I don't know why you are getting the message followed by nothing. If you look in the system folder within your application (or Claris) folder you should see a collection of files of the form fmbmp32.flt where the letters after fm indicate the file extension that the filter is supposed to deal with. In my folder I have filters for bmp, gif, pcx, tiff, cgm, hpgl, pic, wmf, drw, mac, sld. If you right-click the filter file select properties the version tab will tell you what the filter is for, if it is not obvious. jpg is not one of the filters but bmp is, so why you cannot import a bmp file I don't know. Have you applied all the available and appropriate updaters to your version 3?
  6. There is another way which I found by accident. Select the body tab use the fill colour in the status area to set one background, as normal; and use the line colour in the status area to set the alternate background.
  7. The simplest way, I think, is to open a command prompt travel to the directory you are interested in and then issue the command dir /X. That gives you two columns of names (on the right) the first column is the DOS name and the second column is the long filename. If the long file name satisfies 8.3 already then there is no entry in the first column,
  8. Try replacing "Program Files" by the old-fashioned DOS name Progra~1. You will probably have to do the same with other elements of the path which contain spaces.
  9. I'm not sure if I have understood the question correctly but I have made a modification to the auto-enter in your file. Is that the sort of thing you are looking for? LookUpOr2.zip
  10. If you always round up then you can introduce rounding errors. For example 1.5 cents rounds up to 2 cents, 2.5 cents rounds up to 3 cents. Add the two together and you find 4 cents becoming 5 cents. Rounding error can be reduced by leaving rounding until you have completed all other operations but the practice of always rounding up at .5 leads to inevitable errors. To reduce the effect of this simple rounding error you need to round up half the time and round down half the time and the even/odd choice is the common way of doing that. Note that it does not remove the errors it balances the effect.
  11. In File > file options on the open/close tab there is an option to Switch to Layout and a drop-down list of layouts to choose from when you have checked the box.
  12. One method - probably you will see many others before too long. Make a global text field in your table: Small with value "small". Make a second occurrence of the table in question, SMALL say, and then relate the size field in SMALL to the global Small and define SmallCount as an unstored calculation Count(SMALL::size). Copy that for medium and large.
  13. Do the same thing as you do in Access with appropriate changes to reflect the function names in Filemaker. For example suppose you have fields Name, Address1, Address2, City, PostalCode then define an unstored calculation field EnvelopeAddress = Name & "¶" & If(IsEmpty(Address1);"";Address1 & "¶") & If(IsEmpty(Address2);"";Address2 & "¶") & City & "¶" & PostalCode I'm assuming Name City and PostalCode are not empty but if they could be do the same calculation for all address lines.
  14. This is not a resolution just a few remarks since you seem to be working on your own here. Your If calculation should return either an abbreviation or nothing so how does it return Alberta? To me that seems to indicate that the If is not being evaluated. So go back a step and check out the Case function. This part of the case is evaluated if the international_Addressing::city_line is empty could the problem be here?
  15. If it is a strictly 13-digit number you could perhaps do a range validation 1 followed by 12 zeroes up to 13 9's
  • Create New...

Important Information

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