Re: Importing .TAB files from OS9 runtime to OSX?



In article <1139458036.436294.41510@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"Daniel" <4horsemen@xxxxxxxxx> wrote:

I work for a public agency and we have about 500 computers at 200 sites
running an FM Pro runtime app written for OS9.

Many users are converting to OSX and want to run the OS9 app in Classic
Mode on their OSX boxes. There are plans to create a native OSX
runtime, but that probably won't happen until the Summer for various
reasons.

When I export a tab-delimited file from an OS9 box, other OS9 boxes can
see it. But when I try to Import on an OSX machine, running the OS9
runtime app under Classic mode, it doesn't see the tab-delimited file.
Even choosing files of type "All" or "tab-delimited," it's as if the
file simply doesn't exist for the OS9 runtime shelling out of OSX. It
doesn't see it on a USB drive, doesn't see it on the Desktop...although
the file is certainly there, and happily imports back into a native OS9
machine.

This has happened on every one of our OSX machines I've tried. Any
ideas? Thanks!

I'm not sure, but perhaps ".TAB" is a special Mac OS X filename
extension and so those files remain hidden.

It doesn't matter whether or not it is though. An exported file from
FileMaker in Tab delimited format is really just a plain text file, so
it should simply be caled "{filename}.TXT".

Of course, you don't need to export anything at all. Simply copy across
the actual FileMaker data and runtime files and it should work fine.
(You may also need some extra bits that hide in the Mac OS 9 System
Folder to be copied across to the Classic System Folder under Mac OS
X.)


It depends on what version of FileMaker Developer (or whatever it's
called these days) that you're using, but you may already have the Mac
OS X version on the install CD - FileMaker 5.5 for example installs
natively under Mac OS 9 and Mac OS X. This means you can install that
on a Mac OS X computer and create the Mac OS X runtime application ...
if you use the same binding key codes you can even use the same data
files from the Mac OS 9 version since it's only the actual runtime
application that changes. Since it is a runtime application you're
allowed to distribute it to as many users as needed without worrying
about license problems. (Mac OS X runtime applications can only be
created on a Mac OS X computer, Windows runtime applications can only
be created on a Windows computer and Mac OS 9 runtime application can
only be created on a Mac OS 9 computer ... but the actual data files
are all the same - ordinary FileMaker documents, unless you're doing
something funny to protect them).


Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)
.



Relevant Pages

  • Re: How to double boot 09 = 10?
    ... Very few new Mac models will not run OS9 'native'. ... versions of Toast will not run properly on OSX in Compatability Mode ... External Firewire drives are fine for storage and backup, ...
    (microsoft.public.win2000.macintosh)
  • Re: Psychometribabble
    ... I like OS9 best but everyone else who uses a mac likes OSX. ... operating the updated/superseded software: Indesign, Dreamweaver, ...
    (uk.rec.sheds)
  • Re: Would it be worth doing?
    ... finding a copy of OSX on eBay and some bigger PC100 SIMMS (would they ... particully as browsers effecivly stopped for os9 a few years back. ... quite an old bit of kit whether it was PC / Mac). ... back of case is hatch add memory, mac os even tells you which slot ...
    (uk.comp.sys.mac)
  • Re: Dr. OHO
    ... Microsoft isn't supporting explorer on the mac and they tell everyone to go ... If only I wasn't so wedded to my OS9. ... I've got a laptop running OSX tiger with nice shiny new software but, ...
    (uk.rec.sheds)
  • Re: spyware on macs ?
    ... OSX is a rock, there is no ... > Mac virus than it would for a Windows virus. ... but none of those ports have facilities to breach ...
    (comp.sys.mac.advocacy)