Jump to content

GibsonCRG

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by GibsonCRG

  1. Hi - I wondered if you solved your printing problem, with the cutoff text on random records. I've run into exactly the same thing, running FMP 6.0. On occasional records, with no discernable pattern I can make out, the text appears to be "cut off". Looking more closely at what's happening, it appears that a "bounding box" for the text is being set in the correct size and locatio, but the actual text starts printing offset about 0.5 to 0.9 lines too low (relative to the upper left corner of the invisible "bounding box". Then, when the last line of the text prints, you only see that upper portion of those letters - the remainder is being "clipped" by the boundaries of the rectangle that the text WOULD have fit within, had it been properly started at the upper left corner of the field. In other words, the SIZES of each field are being set correctly, but for some reason the text within random fields is offset within the field, causing the edges to get clipped. Anyway, this sounds like the problem you describe, and wonder if you found a fix? I've checked the text formats etc on each problem record, but everything is fine. Moreover, it displays properly in the Print Preview mode - it's just when actually printing to the printer that the text weirdness happens. I wonder if there might be a problem with the printer driver, but the two HP printers we're using are pretty bulletproof in all other printing. ..Chris..
  2. Terrific approach - so simple, I only HOPE I would have figured it out before a month went by, but I doubt it. Thanks for a great approach - works like a charm.
  3. Absolutely! It was a fine example and very informative. Thanks! ..Chris..
  4. Good suggestion, Bruce - the combination of the portal, the global field, and the "fake" list view seems right on target. You really hit it right on the head in terms of why I was trying to avoid dropping "users" into the Find window - it just seems to confuse and/or annoy the users, depending on what they try to do in there. Many thanks - it sounds like you have indeed "been there, done that!" ..Chris..
  5. Doing a "find" for the owner is what I'm after - however, I want to automate the process for the user as much as possible. Unfortunately, the owner list is dymanic, so it's not practical to have a seperate find script for each owner; conversely, the users are newbies, to some extent, and I'd prefer to avoid sending them into a "Find" mode window if I can avoid it. ..Chris..
  6. What I'm after is a bit of an "interactive" browsing experience for users that are using this database as an end-user application, and don't have the familiarity with FileMaker to execute "Finds" on their own. What I'm really trying to do here is to allow the users to dynamically "filter" the data being displayed to them, rather than asking them to sort ALL the records by user and then scroll down to wherever their name happens to fall. I'm pondering the "portal" approach now; I've just been trying to minimize the number of related databases on general principles. Cheers! ..Chris..
  7. Hello FM'ers - I've come across an obstacle, and I fear I just haven't gotten the right basic level of abstraction in my mind to tackle this. I have a list of records displayed in a standard layout, using a "find" criteria (e.g., all "active" issues). Now, each issue has an owner and a title. What I'm trying to do is to have a control of some sort in the header area of the layout where a user could select an item from a value list based menu to execute a "find" based on that value. For instance, when I first display my list, I see ALL the records by all owners (but just the "active" ones); then I go to my "control" in the header, select "Chris", and now I see all the records that are both "active" (from the original find) and also owned by "Chris" (by a new find, based on the value I just chose). I've run into a number of snags, but mainly it's that I can't seem to figure the right way to put this sort of control up in the header section - I'm presuming since it's not part of any given record. Any inspiration from the gurus would be appreciated. Cheers! ..Chris..
  8. Thanks for the good words; my early days of programming taught me that modulo arithmetic comes in handy in all sorts of odd situations. However, I still feel a little bit bad that I've created code with a known Y10K bug! ..Chris..
  9. > It sounds like something else is happening... > or is there as custom alue list somewhere? I don't think anything else is happening, and it's a very bare bones file. I think I found the root of the problem. In the FileMaker help file, it states: FileMaker Pro sorts value list items created from values in a field alphabetically, and duplicate values are not displayed. This seemed to crush my hopes at first blush, but then I came up with a solution that wound up working! While no one is going to accuse me of finding the simple way to do it, here's my solution; hopefully it may do someone some good down the road (plus, I'd love to see if there's a simpler way to do it). First, a little more background on the problem: each of my text entries begins with a TEXT representation of the date the entry was made, then the entry text itself. Dates, of course, do NOT sort well as text - December appears before February, years don't come into play, and so on. Since I need to sort with the most recent dates first, I had to generate a sort key that would work for me. In the History file, I created a SortKey field, calculated as follows: NumToText( Mod( 1000000000, Year(Date)*10000+Month(Date)*100+Day(Date)+ (Hour(Time)+Minute(Time)/60+Seconds(Time)/3600)/100 ) ) This generates a number that, up through the year 9999 or so, will give a LOWER value number for the more RECENT dates. In other words, if sorted using alphabetic rules, the most recent dates will be first in the list, and the older dates will be last in the list. Then, in my MainFile, I told it to build the ValueList with the following attributes: - use only related items from the relationship to the HistoryItems file - use the HistoryTextItem as the first item in the value list - use the SortKey as the second item in the value list - sort the values by the Second Field There appears to be a feature (or bug, I'm not sure) in FileMaker 5.5 such that, when building a dynamic value list from related items, if you have the value list set to "also display values from", the second item is NOT included in the dynamic value list! That's my FileMaker thought for the day. Cheers! ..Chris..
  10. First, I have to say this board is a terrific resource; I got a long way on my problem just reading through prior posts. Many thanks to all. But, I got to one issue I couldn't seem to resolve. I'm creating a Value List from related records, using the formula I cobbled together from prior posts here to form a text result that concatenates the related values from the "History Items" database: Substitute( ValueListItems( Status( CurrentFileName), "History Items Value List" ) , "
×
×
  • Create New...

Important Information

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