Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 6848 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I've noticed that when some FM7 solutions are converted to FM8, an FM8A Database Design report yeilds some interesting results:

In the script section of the design report, under the heading "Fields used in this script", it often lists "" as an itemized entry, despite there being no missing field within the script itself.

I would guess that somewhere along the line, when removing actual missing fields, there is some remnant left behind that FM8 is picking up on. Has anyone else experienced this?

Any idea how one might go about cleaning up such files?

Thanks! :P

  • 1 month later...
Posted

I just encountered this problem. Since "ahhwhereami" confirms I'm not alone, I submitted this formal problem report to FileMaker:

I'm using the DDR Report on a large database converted from FM7 and enhanced in FM8A, attempting to locate errors by searching for "

For some scripts, the DDR Report is erroneously reporting "" in the "Fields used in this script" for some scripts. However, I've carefully inspected the scripts, and there is no reference to a missing field.

-- Ward

  • 2 weeks later...
Posted (edited)

During my latest scan for missing/unknown errors, I discovered the "" problem is worse than I thought.

In the case of an actual missing field in a script, the "Script Steps" section of the DDR shows "", while the "Fields used in this script" section fails to mention the missing field.

So it appears "" is always a bogus report.

-- Ward

P.S. I tried to submit an updated formal bug report to FileMaker, Inc., but their Report Product Problems page reports an "Unexpected Error" in "... database db_feedback.fp5". Hmmm.

Edited by Guest
  • 3 months later...
Posted

This problem just keeps getting worse.

I've now discovered my HTML DDR is reporting ...

Layouts used in this script:

However, there's no error in the script.

Posted

I'm confused. If I'm reading you correctly, something just isn't adding up here.

You stated, or at least I assumed because you hijacked a post that stated it, the fie files were created in v7 and modified in v8. Yes or no?

If yes, why are you using a extension of .fp5 in your latest post?

If this is a multi-file database that was "Converted" to v7 from an earlier version, it might explain what you are experiencing now.

If not, then a better explanation, example of the files involved, copy of the DDR, etc. might help us see what you are seeing.

It doesn't make sense that the script is showing a layout that the DDR shows as missing.

Lee

Posted

You stated, or at least I assumed because you hijacked a post that stated it, the fie files were created in v7 and modified in v8. Yes or no?

I didn't hijack; I added additional information to the initial report. I created my original database in FM 7 Dev and upgraded it to FM 8 Advanced.

If yes, why are you using a extension of .fp5 in your latest post?

The .fp5 extension came from an error message at the FileMaker site, where they were apparently using quite an old database to for the (failing) feedback system.

If this is a multi-file database that was "Converted" to v7 from an earlier version, it might explain what you are experiencing now.

If not, then a better explanation, example of the files involved, copy of the DDR, etc. might help us see what you are seeing.

It doesn't make sense that the script is showing a layout that the DDR shows as missing.

The DDR is showing the layouts referenced in the script. It's also show a "ghost" missing layout (like the "ghost" missing fields in the earlier reports).

The essence of this thread is the FM DDR is erroneously reporting missing items in some database files converted from FM 7 to FM 8.

Posted

I haven't experienced this problem, and from the looks of things not may others have either.

If it isn't a bug, then I suspect that it is a corrupted file.

Can you attach a couple of screen shots for us to look at.

Lee

This topic is 6848 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.