Dialoglist in web forces login

Hi all,

database A has documents which should be read also by web users. They have reader access to that db and will open the docs only in read mode. When they try to open a doc in the web, they get a login dialog (so they do not have access).

The reason is an editible (for the admins) dialog list in the form which gets its choice list from database B (dblookup). The web users do not have access to that db.

Which makes me a bit “hopeful” is the entry in the server log: ATTEMPT TO ACCESS DATABASE by was denied

Servername, not Webusers name! But this is confusing: the server has Manager access to database B.

I am looking for “the correct way” to solve this - I know that I can create another webform for these docs which offers that field in a simple text field and not in a dialog list, but that would force me to maintain 2 forms parallel in the future …

Thanks for any help in advance

Uwe

Subject: Dialoglist in web forces login

You want something simple?Make two subforms and display whichever one is appropriate to each group.

@if(@username=“Anonymous”;“ReadOnlySubform”;“EditingSubform”)

If your web folks are loging in, then your easiest option is to add a role for the superuser group… maybe [admin]? Then the formula would be:

@If(@IsMember(“[admin]”;@UserRoles);“EditingSubform”;“ReadOnlySubform”)

If you are using the same form for web/notes and want it readonly for all web users:

@If(@IsMember(“$$WebClient”; @UserRoles); “ReadOnlySubform”;“EditingSubform”)

The EditingSubform is all the fields as they are now, moved onto a subform.

The ReadOnlySubform is all the fields replated with computed for display fields with their fields changed just a bit… so Firstname becomes Firstname_Display… or whatever

You could use a controlled-access section, instead of subforms, then setup the rules for who can edit or not… search “Creating controlled-access sections of forms” in designer help.

:smiley:

Subject: RE: Dialoglist in web forces login

thanks Stan for your response,

2 forms is the thing I want to avoid - due to maintaining twice.

I helped myself now in the form itself in the “oneandonly” form with an computed for display field an hide-when formulas for those 2 fields.

What really wonders me is

  • that a choice list in a dialog list is already “executed” in read mode,

  • the access violation in the log file

Uwe

Subject: RE: Dialoglist in web forces login

You could modify your lookup code so it doesn’t execute when it’s not needed… for example, something like this speeds loading of the form:

@If(!@IsNewDoc & @IsDocBeingLoaded; @Unavailable; @DbLookup…

You could easily add

!@IsDocBeingEdited;

regarding the server error in your log… try posting that as a separate question in the forum… I have no idea why you got that