dbTalk Databases Forums  

File refs w/ local and server files

comp.databases.filemaker comp.databases.filemaker


Discuss File refs w/ local and server files in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
audleman@quasika.net
 
Posts: n/a

Default File refs w/ local and server files - 07-18-2005 , 02:59 PM






I've been developing a multi-file database on my PC, and have gotten to
the point where it's time to upload it to a server machine and start
sharing it over Filemaker Network with FM Server 7. Since I've been
developing on a stand-alone laptop, all of my file references look like
so:

file:Contacts.fp7
file:../Donors/Donors.fp7

Now that the files are on the server, they seem to find each other just
fine with the 'file:' prefix, but there is one problem. When I try to
develop on my local machine, it often finds my local files instead of
the server ones.

I see that another way of setting up file refs is to use the 'fmnet:'
prefix. That seems like a good thing to use, but what will happen when
I download the files back to my laptop for development away from the
office? Will they be able to find each other?

Can anybody tell me the proper way to set up file references in this
situation?

Thank you,
Kevin


Reply With Quote
  #2  
Old   
Lynn allen
 
Posts: n/a

Default Re: File refs w/ local and server files - 07-18-2005 , 03:23 PM






audleman (AT) quasika (DOT) net <audleman (AT) quasika (DOT) net> wrote:

Quote:
I've been developing a multi-file database on my PC, and have gotten to
the point where it's time to upload it to a server machine and start
sharing it over Filemaker Network with FM Server 7. Since I've been
developing on a stand-alone laptop, all of my file references look like
so:

file:Contacts.fp7
file:../Donors/Donors.fp7

Now that the files are on the server, they seem to find each other just
fine with the 'file:' prefix, but there is one problem. When I try to
develop on my local machine, it often finds my local files instead of
the server ones.

I see that another way of setting up file refs is to use the 'fmnet:'
prefix. That seems like a good thing to use, but what will happen when
I download the files back to my laptop for development away from the
office? Will they be able to find each other?

Can anybody tell me the proper way to set up file references in this
situation?
Generally, one doesn't have both hosted files AND local files in
development. If you're going to continue to develop on the hosted files,
zip or stuff all local copies and that will solve your problem.

I would also be VERY careful of developing on hosted files. There are
many reliable reports that interruptions or network conflicts during
schema changes on hosted files can result in catastrophic effects,
including but not limited to having all field definitions, all scripts,
or all data disappear from the files in question.

Run frequent server backups during development and if you DO have a
glitch, return to the most recent good version of your files.

I personally try to develop using the separation approach, where data
files are separate from interface files, and most work is done in the
interface files, which don't require any importing when they're uploaded
to the server. This way I work solely in my local copies, and upload as
needed.

That way I can work with my copy of FM set to "none" in the network
protocol, and not interact with the hosted files while I work.

Lynn Allen
--
Allen & Allen Semiotics www.semiotics.com
FSA Associate Filemaker Design & Consulting


Reply With Quote
  #3  
Old   
42
 
Posts: n/a

Default Re: File refs w/ local and server files - 07-18-2005 , 04:21 PM



In article <1gzwcx9.u16dyu1g7jji8N%lynn (AT) NOT-semiotics (DOT) com>, lynn@NOT-
semiotics.com says...

Quote:
Can anybody tell me the proper way to set up file references in this
situation?

Generally, one doesn't have both hosted files AND local files in
development. If you're going to continue to develop on the hosted files,
zip or stuff all local copies and that will solve your problem.
/agreed

Quote:
I would also be VERY careful of developing on hosted files. There are
many reliable reports that interruptions or network conflicts during
schema changes on hosted files can result in catastrophic effects,
including but not limited to having all field definitions, all scripts,
or all data disappear from the files in question.
There are about as many reports of people who swear by working on hosted
files because they aren't damaged and don't need to be scanned (or god
forbid) "recovered"... er "abandoned" if the local desktop crashes.

Its also key to point out that working on hosted files doesn't
necessarily mean you are working on LIVE files.

Quote:
Run frequent server backups during development and if you DO have a
glitch, return to the most recent good version of your files.
/AGREED

Of course, thats true of any any development in any situation.

Quote:
I personally try to develop using the separation approach, where data
files are separate from interface files, and most work is done in the
interface files, which don't require any importing when they're uploaded
to the server. This way I work solely in my local copies, and upload as
needed.
/agreed

Me too. Although even with the separation approach I find you'll have to
make changes in the 'data' files fairly often especially if you make
much use of the field defintion options for validation, auto-enter, etc.

Quote:
That way I can work with my copy of FM set to "none" in the network
protocol, and not interact with the hosted files while I work.
Actually unless I'm mistaken, the protocol setting in 7 now only affects
files you host (or don't host). You can open hosted files even if
protocol is set to none... you just can't host them.





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.