AnsweredAssumed Answered

REAL Bug: Adding [:] in a table name, brakes MERGE FIELD relationship

Question asked by inicksf on Apr 25, 2009
Latest reply on Jan 4, 2019 by danshockley

Like • Show 0 Likes0
Comment • 8

Summary

Description of the issue

Adding ':' in the table name is not prohibited by any Filemaker warning...Doing so, all seems to work fine, except MERGE FIELD: Inserting merged field in a layout as: , continue to show instead of the field's data ... After to have burnt my brain per hours, and pray all Gods known, I have fixed this trouble.Why I know this is a real bug?I have added ':' in some of table names of my Database, thinking to present its better later in my development.Then, all merged fields I have put in my layouts before the add of the [:] was working well, only new merged fields added AFTER the add didn't work...Worth ! Just the edition of a merged field by double-click on it, then validate it, was enough to "brake" it and show the even in "browse" mode... DO NOT PUT ':' IN TABLE NAME

No one else has this question

Outcomes

TSGal Apr 27, 2009 2:19 PM

inick06:

Thank you for your post.

Our Development and Software Quality Assurance (Testing) department are aware of this issue, but no additional information is available at this time. Until this is changed, remove any colons from table names.

TSGal

FileMaker, Inc.

Actions

mw_1 Feb 20, 2010 9:13 AM

Almost a year on and this is an issue still - I'm using FMP Advanced 10.0v3.

I tried to use a field from a relationship in a merge field and the "::" gets expanded to the current time when I access a field from a relationship with a ":" in its name.

This works fine:

Project <<UI::g.ProjectName>>

This fails:

Project <<UI:Meetings::ProjectName>> gets displayed as Project <<UI:Meetings17:05:23ProjectName>>

Actions

TSGal Feb 22, 2010 12:40 PM

mw:

No additional information is available at this time. A colon in a merge field will still not work as expected.

TSGal

FileMaker, Inc.

Actions

mw_1 Mar 4, 2010 6:58 AM

Thanks TSGal - can you please confirm which characters I'm allowed to use in a table name without breaking the merge field functioanlity?

Cheers

Michael

Actions

TSGal Mar 4, 2010 8:23 AM

mw:

I only see colons in the table occurrence name causing a problem. That doesn't mean other characters will cause a problem, but the colon is the only character reported that causes the problem. Sorry I can't be more definitive. If you find another character that makes this fail, please let me know.

TSGal

FileMaker, Inc.

Actions

philmodjunk Jun 25, 2012 3:51 PM

This bug does not occur in FileMaker 12.

Actions

alex_zueiv Jun 25, 2012 10:58 PM

Colon sign (:) in a table occurrence name also breaks functionality of the script step Set Field By Name []. In script debugger it returns error 102 (Field is missing). This issue exists in FMP 12v1 too.

Actions

danshockley @ alex_zueiv on Jan 4, 2019 7:01 AM

In FileMaker 17.0.3, the FieldType function fails when used with a field whose table occurrence has a single colon in it. Using FieldType on the same field, but with a table occurrence without a colon works as expected.

Actions

8 Replies

TSGal Apr 27, 2009 2:19 PM
Mark Correct
Correct Answer
inick06:

Thank you for your post.

Our Development and Software Quality Assurance (Testing) department are aware of this issue, but no additional information is available at this time. Until this is changed, remove any colons from table names.

TSGal
FileMaker, Inc.
Like • Show 0 Likes0
Actions
mw_1 Feb 20, 2010 9:13 AM
Mark Correct
Correct Answer

Almost a year on and this is an issue still - I'm using FMP Advanced 10.0v3.

I tried to use a field from a relationship in a merge field and the "::" gets expanded to the current time when I access a field from a relationship with a ":" in its name.

This works fine:
Project <<UI::g.ProjectName>>

This fails:
Project <<UI:Meetings::ProjectName>> gets displayed as Project <<UI:Meetings17:05:23ProjectName>>
Like • Show 0 Likes0
Actions
TSGal Feb 22, 2010 12:40 PM
Mark Correct
Correct Answer
mw:

No additional information is available at this time. A colon in a merge field will still not work as expected.

TSGal
FileMaker, Inc.
Like • Show 0 Likes0
Actions
mw_1 Mar 4, 2010 6:58 AM
Mark Correct
Correct Answer
Thanks TSGal - can you please confirm which characters I'm allowed to use in a table name without breaking the merge field functioanlity?

Cheers
Michael
Like • Show 0 Likes0
Actions
TSGal Mar 4, 2010 8:23 AM
Mark Correct
Correct Answer
mw:

I only see colons in the table occurrence name causing a problem. That doesn't mean other characters will cause a problem, but the colon is the only character reported that causes the problem. Sorry I can't be more definitive. If you find another character that makes this fail, please let me know.

TSGal

FileMaker, Inc.
Like • Show 0 Likes0
Actions
philmodjunk Jun 25, 2012 3:51 PM
Mark Correct
Correct Answer
This bug does not occur in FileMaker 12.
Like • Show 0 Likes0
Actions
alex_zueiv Jun 25, 2012 10:58 PM
Mark Correct
Correct Answer
Colon sign (:) in a table occurrence name also breaks functionality of the script step Set Field By Name []. In script debugger it returns error 102 (Field is missing). This issue exists in FMP 12v1 too.
Like • Show 0 Likes0
Actions
danshockley @ alex_zueiv on Jan 4, 2019 7:01 AM
Mark Correct
Correct Answer
In FileMaker 17.0.3, the FieldType function fails when used with a field whose table occurrence has a single colon in it. Using FieldType on the same field, but with a table occurrence without a colon works as expected.
Like • Show 0 Likes0
Actions

REAL Bug: Adding [:] in a table name, brakes MERGE FIELD relationship

Summary

Description of the issue

Outcomes

Related Content

Recommended Content