Hi Dee,

Happy Holidays!

First, let me say that I don't know the exact naming convention of ebase
v1.03, so I may have the filenames wrong.  Also, what I'm telling you
here is also described on the FAQ page of the ebase site, so if you have
any problems, you can refer to the appropriate FAQ.  Lastly, go ahead
and make a backup of the entire ebase folder before monkeying with it.

In answer to your question about whether or not ebase 1.03 files will
automatically open with Filemaker out of the box, well, sort of.  The
ebase files are converted and ready to go with Filemaker 5.0, but if you
just double click them (for example, double clicking on ebase.103), I'm
betting they will still run as a runtime application.

I haven't used the new version, but here's how the old version worked,
and I assume the new version is the same.  All of the ebase files are
"mapped" to the runtime file (the ebase.exe file, not the ebase.103
file) so that when you double click on the ebase.103 file it will look
for ebase.exe to open it (not Filemaker).  

This means you have to delete the mapping of the ebase files to the
ebase.exe file and re-map them to Filemaker.  To do this, as I recall
it, you need to go into Windows Explorer, click View->Folder
Options->File Types, then scroll to find the 103 file type (this refers
to the dot extension, .103).  Hint - if you select the ebase.103 file
before going into Windows Explorer, I believe the File Types option
opens with the .103 file type already selected.  In any case, select
that file type (.103), click Remove or Delete (to delete this mapping)
and say yes to the Are You Sure dialog box.  Now, when you look at your
ebase files, they should have the generic windows icon (because they are
no longer mapped to any program).

Next you have to re-map the files to Filemaker.  To do this you can do
one of two things.  One, you can double click on the ebase.103 generic
file icon.  Since the computer no longer knows how to open it, it will
give you the Open With dialog box.  Choose Filemaker 5.0 to open the
file and check the box that says "Always use this program to open this
file."  Checking this will "map" all files with that extension to
Filemaker.  The second way is to right click the file (instead of double
clicking it).  In the Context menu that pops up, select Open With... 
This will give you the same Open With dialog box.  Proceed as before.

Once you've done this mapping, the ebase files should all have the
Filemaker icon and you should be able to double click the ebase.103 file
to open ebase with Filemaker.  If this works properly, you can also
create a shortcut for the ebase.103 and put it on your desktop for
easier navigation.  In fact, I've gone a step further and dragged the
ebase shortcut to the Task Bar at the bottom of the Windows screen. 
This puts the ebase icon on the Task Bar which let's me launch ebase
with one click right from Windows without cluttering up my desktop.

One more thing.  Assuming you no longer need the ebase.exe runtime
application, you can now safely delete it (although it shouldn't hurt to
leave it on your hard drive).  But, go ahead and make a backup of the
runtime before deleting it.

Hope this helps.  I've copied the listserv in case anyone else out there
has the same question.

Carl

Dee Christoff wrote:
> 
> Carl,
> Hi. Remember me?
> Now that things have settled down after the holidays, I've finally downloaded the 
>new ebase version and deleted anything else I had.  (I didn't have any records in it 
>because I had all sorts of problems getting it running.) Anyway, do I understand 
>correctly that I now do NOT need to physically open FMP 5.0 FIRST in order to open 
>e-base? (When I downloaded it, I saved it in a "Downloads" folder I created. OR, do I 
>need to put it in FMP 5.0 somewhere? If I remember correctly, the new version is 
>"automatically" read by FMP is this correct? Do you know?
> THANKS! Happy New Year!
> Dee
> 
> >>> Carl Paulsen <[EMAIL PROTECTED]> 12/12 12:17 PM >>>
> Dee and others,
> 
> Ebase v.1.00 and 1.02 ARE compatible with FMP 5, you just need to
> convert the files by opening them in FMP5.  With care, you can convert
> your copy of ebase without downloading it over again.  Directions are on
> the ebase website FAQ page.
> 
> As I understand it, the new version (1.03) is just a converted copy of
> ebase w/ a few bugs from 1.02 fixed.  If you're still having problems,
> go ahead and download again.
> 
> Carl
> 
> Dee Christoff wrote:
> >
> > Bob or Others,
> > Are you saying that earlier versions of ebase are not compatible with FMP 5.0? If 
>so, maybe that's the source of all the problems I've been having!!!! I mentioned that 
>I was using FMP 5.0 in my postings... Hmmmmmmmm....
> >
> > Good time for me to dump it all and start over. Glad I didn't waste my time doing 
>it last week.
> >
> > Dee Christoff
> > Director of Development
> > Washington Poison Center
> > [EMAIL PROTECTED]
> >
> > >>> Bob Schmitt <[EMAIL PROTECTED]> 12/12 10:23 AM >>>
> > Yes. The Filemaker Pro 5 file format is not compatible with earlier
> > versions. That's the main reason we did this release: you can't
> > purchase earlier versions of Filemaker anymore.
> >
> > bob
> >
> > At 1:05 PM -0500 12/12/00, Melissa Victory wrote:
> > >Sorry to be so stupid, but is it true that you have to have
> > >Filemaker 5.0 to use the new version?
> > >
> > >Just wondering.
> > >
> > >Thanks!
> > >
> > >Melissa Victory
> >
> > --
> > -----------------------------------------------------------------------------
> > Bob Schmitt, TechRocks
> > 38 South Last Chance Gulch - Suite 2A Helena MT 59601-5029
> > Voice: 406.442.3687             Email: [EMAIL PROTECTED]
> > eFax: 520.832.1047              Web: http://www.techrocks.org
> > ----------------------------------------------------------------------------
> 
> --
> Carl Paulsen
> New Hampshire Rivers Council
> 54 Portsmouth Street
> Concord, NH  03301
> 603-228-6472
> 603-228-0423 Fax
> [EMAIL PROTECTED]

-- 
Carl Paulsen
New Hampshire Rivers Council
54 Portsmouth Street
Concord, NH  03301
603-228-6472
603-228-0423 Fax
[EMAIL PROTECTED]

Reply via email to