Calc Fields and references to databases with #s in name

[ErikP]

I've inherited a fairly complex database with some screwy naming conventions. The main database is named "1.22.98 Design.fm5".

I'm working on a new database with a relationship to this one. When I try to set up a calculation field in the new database and incorporate fields from the old database I get the error message "This number cannot be evaluated" and it then highlights the "1.22.98" portion of the database name. Is there any way of getting FM to accept this file name as is or am I going to have to rename it? If so, it will be a nightmare setting up all of the relationships to the old.

Thanks for any input.

Erik

[danjacoby]

When you (or whoever) set up the relationship, a message should have appeared saying "This name cannot be used in a calculation...", stating four possible reasons, one being that the name of the related DB begins with a number.

It's one reason I never begin FMP filenames, fields, scripts -- heck, anything -- with a number. (Yeah, yeah, the contents of a number field...)

A second caveat -- not a good idea to put empty spaces in filenames, fields, et cetera; that can be confusing, too.

My suggestion -- bite the bullet, and rename the offending files.