Hi,

For your information...

The following FMP Functions fail in FMP 10.0v3 on a Mac -- if the name of the file that contains them has a period (.) in its name.

FieldBounds( Get( FileName ) ; Get( LayoutName ) ; "myField" ) & ¶ & // put in the name of your Field
FieldComment( Get( FileName ) ; "myField" ) & ¶ &
FieldIDs( Get( FileName ) ; Get( LayoutName )) & "¶--------¶" &
FieldNames( Get( FileName ) ; Get( LayoutName )) & "¶--------¶" &
FieldRepetitions( Get( FileName ) ; Get( LayoutName ) ; "myField" ) & ¶ &
FieldStyle( Get( FileName ) ; Get( LayoutName ) ; "myField" ) & ¶ &
FieldType( Get( FileName ) ; "myField" ) & ¶ &
GetNextSerialValue( Get( FileName ) ; "myField" ) & ¶ & //field that has auto-enter serial# specified
LayoutIDs( Get( FileName )) & "¶--------¶" &
LayoutNames( Get( FileName )) & "¶--------¶" &
LayoutObjectNames( Get( FileName ) ; Get( LayoutName )) & "¶--------¶" & // must have an object named on the layout
RelationInfo( Get( FileName ) ; Get( LayoutTableName )) & "¶--------¶" & // must have at least one TableOccuranceGroup
ScriptIDs( Get( FileName )) & ¶ &
ScriptNames( Get( FileName )) & ¶ &
TableIDs( Get( FileName )) & ¶ &
TableNames( Get( FileName )) & ¶ &
ValueListIDs( Get( FileName )) & ¶ &
ValueListItems( Get( FileName ) ; "myValueList" ) & ¶ & // put in the name of your ValueListName
ValueListNames( Get( FileName )) & ¶ &
""

All these work fine on a file name called "Test.fp7".

They return nothing on a file name called "Test.One.fp7".

The Function "DatabaseNames" does not fail. Any Function that requires 'fileName' fails.

I don't know if this fails for Windows.

The only reasonable workaround seems to be to have a Startup Script that detects a "dot" in its FileName and notify the user...

Steven
--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/