Form Problem svy_nav_c_main

Hi

I constantly have this error, that prevents me from exporting the solution. Any idea, how it can be solved?

Description Resource Path Location Type
Related tab error: form “svy_nav_c_main” is based on a different table then relation “_to_nav_popmenu$main_report”. svy_nav_c_main.frm /svy_nav_configurator/forms svy_nav_configurator/forms/svy_nav_c_main.frm Form Problem

Thanks for any help
Fritz Maurhofer

Servoy Version 6.0.5 - build 1230

Hi Fritz,

I never got this error. So I think something in your solution is changed. Does your “_to_nav_popmenu$main_report” relation look like this:

[attachment=0]relation.png[/attachment]

Hi Sanneke

It allmost looks like that, the prefix “scopes” is missing (but there aren’t any “scopes” at this place, at least I can’t see any).

[attachment=0]_to_nav_popmenu$main_report.PNG[/attachment]

Fritz

Well the scopes is in 6.1, you might still be in 6.0.7.

Hi Sanneke

yes, for sure, I am, sorry for not mention that.
But anyway, what could be the problem? Any suggestions?

Thanks
Fritz

Is the form ‘svy_nav_c_popmenu_root_tbl’ based on datasource ‘svy_framework.nav_popmenu’?

Does the tab popmenu on form ‘svy_nav_c_main’ still contain ‘svy_nav_c_popmenu_root_tbl’ ?

[attachment=0]tab_contains.png[/attachment]

Good morning sanneke

sanneke:
Is the form ‘svy_nav_c_popmenu_root_tbl’ based on datasource ‘svy_framework.nav_popmenu’?
Does the tab popmenu on form ‘svy_nav_c_main’ still contain ‘svy_nav_c_popmenu_root_tbl’ ?

Yes to both questions.

Cheers
Fritz Mauhofer

If you doubleclick the error in the problems tab, which element is selected in the form editor?

Joas:
If you doubleclick the error in the problems tab, which element is selected in the form editor?

Hi Joas

it opend the form svy_nav_c_main’ exactly as shown in the picture in Sanneke’s message.

But curios enough, for a test I had to export the solution. I deleted the error message (that prevented from exporting), it worked perfect, also the exported solution on the server. Since then, the error just disappeared! No idea what’s happened :? :?
I guess, we have just to wait and see, if it shows up again. Maybe it was just a short headache in the framework :lol:

Thanks for your help. I come back on the issue if necessary.
Fritz Maurhofer