Jump to content

JMP

Members
  • Posts

    9
  • Joined

  • Last visited

JMP's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Seems that a further answer to this question is that a small window can ONLY be kept open over a large window if the large window is not maximized. Or is there something I'm missing?
  2. Windows 2000 Filemaker 7.0v2 8 and 9 point Arial font looks very bad at any zoom level including 100% in preview mode though changing Edit/Preferences/General/Font smoothing style to "Smooth,light" made some improvements.
  3. Found the solution after more digging. It's something about the language used to store the index for the text field. You have to hold down Ctrl+Alt override the indexing language, or something to that effect, while selecting the font. A warning message about this *sometimes* pops up when trying to apply this font format in layout mode. Presumably other symbol fonts such as Wingdings must be handled the same way.
  4. I purchased this font from a postal sortation software company called Postage Saver and have been using it for many years without problem. http://savepostage.com/barfont.html The same font displays perfectly well in Filemaker 6, 5, and 4 on the same machine. I'll try to send you the font attached to a separate private message.
  5. Running Filemaker 7.0v2 on Windows 2000 finding a serious problem with a true type font. The barcode font BARS12.TTF (version 1.00), which works just fine with Filemaker 6 for displaying a postal address label barcode, fails to render in Filemaker 7. An ordinary (plain) text field, in both a new test database and in a converted database I've used for years, refuses to accept formatting to this font in Layout mode, though the font shows in the font list and shows as a truetype font. (In Browse mode text will accept the font formatting, though it does not look right at the standard 12pt font size; appears to render shorter in height and length than normal.) Anyone else run into this? Solutions or workarounds? Must be a software bug...?
  6. What is status of use of Filemaker 7 as ODBC client in general, and on local workstation in particular? Is it possible or is there a workaround besides export of data to earlier version of Filemaker?
  7. Anyone know if it's possible to search for and replace an the end-of-line in a text field when the field has only a single line of text?
  8. So this capability to serve as an ODBC/JDBC data client or source on local host is essentially the same capability that was provided in Filemaker 6?
  9. In response to your posting about JDBC/ODBC support in Filemaker 7 has there been a TechBrief posted yet?
×
×
  • Create New...

Important Information

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