dbTalk Databases Forums  

Wildcard use in File References - bad idea?

comp.databases.filemaker comp.databases.filemaker


Discuss Wildcard use in File References - bad idea? in the comp.databases.filemaker forum.



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

Default Wildcard use in File References - bad idea? - 09-15-2005 , 12:23 PM






FilemakerPro 7 help says

Quote:
FileMaker does not recommend using an asterisk (*)
as a wild card character in network file path
definitions as it slows FileMaker network traffic.
When possible, replace an asterisk with the appropriate IP address.
With this in mind, I hard coded an IP address into the file references
of the 20-odd files in my solution, which comes out to ~80 references.
My file references look like this: fmnet:/10.0.0.65/MyFile

Now my company is a week away from switching our DSL provider. It looks
like the whole range of IP addresses we have been using will have to be
changed, and that means half a day of painstaking file reference
updating.

Surely there's a better way? I have all of the files running on a
single server. Is there a way I can use relative paths to avoid having
to change my references again in the future, but not lose performance?

Kevin



Reply With Quote
  #2  
Old   
FP
 
Posts: n/a

Default Re: Wildcard use in File References - bad idea? - 09-15-2005 , 05:10 PM






My understanding is the files on the server, when they reference each
other, should contain a file reference as;
file:MyFile

Only the local startup file should have the reference you mentioned.


Reply With Quote
  #3  
Old   
Michael Myett
 
Posts: n/a

Default Re: Wildcard use in File References - bad idea? - 09-15-2005 , 07:10 PM



audleman (AT) quasika (DOT) net wrote:
Quote:
FilemakerPro 7 help says


FileMaker does not recommend using an asterisk (*)
as a wild card character in network file path
definitions as it slows FileMaker network traffic.
When possible, replace an asterisk with the appropriate IP address.


With this in mind, I hard coded an IP address into the file references
of the 20-odd files in my solution, which comes out to ~80 references.
My file references look like this: fmnet:/10.0.0.65/MyFile

Now my company is a week away from switching our DSL provider. It looks
like the whole range of IP addresses we have been using will have to be
changed, and that means half a day of painstaking file reference
updating.

Surely there's a better way? I have all of the files running on a
single server. Is there a way I can use relative paths to avoid having
to change my references again in the future, but not lose performance?

Kevin

Why not reference a global field in a preferences file or table. This
way you can change the IP address globally with one edit.

Michael Myett



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.