Profound Logic Forums

Hello,
In the designer using for example "Combo Box" and putting library/database file in properties "Choices Database File", when I try to select "Choices value field" or "Choices option field", I get the error attached image.

Option "Library List", has the correct libraries.

Tks

In my experience this error is caused by a typo in the list of libraries. Since you say the list is correct, it could also be an authority issue. Is the user you're signed in with authorized to all the libraries in the list?

Glenn

You can also get more information on the error by finding your Designer job in the QHTTPSVR subsystem and looking at the job log. You should see a more specific error listed before the one you're seeing in the Designer.

For example, if I try to add a library that I know doesn't exist, these are the errors I see in the job log. Glenn

Another possible cause is putting 'PROFOUNDUI' (or whichever library you installed the product in) into your library list. Since the product will add this library automatically, it will create a conflict if you try to add it as well.

Thanks for your answers . I will review this.

Hi Scott,

Happy new year!

I am a colleague of JPG.
We work with IASP. I think the problem is that when we started the " Visual Designer" is not loading the IASP the connecting user.
Yes that is loaded in the options "Open" , "Convert ", "Save " and " Save As", but when you chose the DSPF, then removes the IASP and works only with the *BASE.

Would it be possible when connected to the "Visual Designer" always keep the IASP the user connecting?.

This is the Joblog for the option "Open" (H9O is the name of IASP):

ASP group H9O established.
Changed the property of PUIMBRLIST object type QTEMP
*USRSPC.
ASP Group set to *NONE.

And this is the joblog for the option "convert" (H9O is the name of IASP):

ASP group H9O established.
ASP Group set to *NONE.

This is the image for a file in *BASE:

[img][/img]

And this is the image for a file in iasp H9O:

[img][/img]


Thanks.

You are correct, Enrique. It appears that the Visual Designer does not set the user's ASP group when retrieving a field listing.

I can look into fixing this... can you tell me what version of Profound UI you are running?

Hi Scott,

we work with last version (Version: 5.0.4).

Thanks.

I have fixed this on our development box. The fix will be included in the next release of Profound UI.