I created a file in Ver8 Advanced on MacOS-Tiger. This is a 6 table
file. On my WinXP Pro machine I turned this into a runtime that I use
from my USB drive at work, which does not have any version of
Filemaker Pro.

The primary use of the file is tracking the utilities for the
company... about 350 accounts nationwide. I went to switch to the
main layout of the Utility table and I got the message about the file
being corrupted and needing to use RECOVER. Since this file is the
runtime version, which I have been continuing the development of
opening it on my Mac at home, Recover doesn't seem to work.

Seems to me, back in the late 90s when I was using a runtime
application in version 3, Recover did work on the rare occasion it was
needed. I am planning to develop some small-scale apps for use in
stand alone restaurants, and this brings up the question what my
customers would do. In the meantime I am curious about my current
situation.

TK

In article <1176172155.333744.286150 (AT) y66g2000hsf (DOT) googlegroups.com>,
"TKnTexas" <tkntexas55 (AT) aol (DOT) com> wrote:

I'm not sure about the answer to your problem. As far as I've found the
Recover command works on runtime files (they are after all really only
normal FileMaker files), but I haven't used many of them and not under
newer versions of FileMaker.

BUT
you shouldn't really continue working with a file that's been
recovered, in any version of FileMaker.

The Recover command is only there to allow you to (hopefully) get the
data back when a file becomes corrupted. After recovering the file
you're meant to import the data from the damaged file into a fresh /
new copy of the file and then delete the recovered file entirely.


As a developer, it is best method is to work ONLY on empty files and
not change the "working" copies that other people have been entering
data into. Once you've got an updated file / system ready you then
import the old data across into copies of the new files, keeping the
original files (and backups of them) as your empty developer version.

Realistically of course this isn't always possible. (


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

As the user and the developer I have been doing both. I am using a 2-
day old copy. I have not been able to do the RECOVER on the damaged
files. It has some changes to layouts that I can reproduce in this
copy. Looking on the menu for the runtime version, there is no
RECOVER option. I would take this to mean that end-users of runtimes
cannot RECOVER.

The runtime databases that are in the folder (ending with TKH instead
of FP7) can they be saved as FP7? This app is a learning app for me.
I am the only user. As long as I dump the utility data to a
spreadsheet, my department is not going to care.

I would appreciate any help on this problem.

On Apr 10, 1:20 am, Helpful Harry <helpful_ha... (AT) nom (DOT) de.plume.com>
wrote:

Trying to answer just a part of the question, I'd say that runtime DBs can
be read with a regular copy of FileMaker, thus having all FM menus. If they
have FP7 extension you can read them by double clicking on them, if they
have TKH extension you just drop down that file on the FM application icon
to making it to be opened by FM - or open FM first then choose the TKH file
to open -.
Everything that Harry said applies though.
Remi-Noel

"TKnTexas" <tkntexas55 (AT) aol (DOT) com> a écrit dans le message de news:
1176224578.898088.111450 (AT) p77g20...oglegroups.com...

In article <1176224578.898088.111450 (AT) p77g2000hsh (DOT) googlegroups.com>,
"TKnTexas" <tkntexas55 (AT) aol (DOT) com> wrote:

I haven't got one to check (and it would be FileMaker 4 anyway), but
the runtime application is a cut-down version of FileMaker and may not
have the "Recover" ability in it.

You should still be able to open the runtime's database file(s) in a
full version of FileMaker (unless you've set some of the privilege
options, in which case you should also have set a Master password to
still give full access to the file).

You can't just double-click the runtime database file though since it's
"bound" to the cut-down runtime application instead of FileMaker Pro.
You can run the fulll version of FileMaker and then use the File ->
Open (or in this case File -> Recover) menu option to open the runtime
database file.

This of course does mean that "end users" can't recover the file using
the runtime application, but then they shouldn't being doing that
anyway since the file is corrupt and the data needs to be imported into
a fresh copy ... which is really something the developer / IT person
should be doing.


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