Hi, I’ve got another problem with a view getting private at first use : I can’t use the @dbcolumn command on it, an error message says that the server will not create the index.However I can display this view without any problem.
Can someone help me with this problem ?
Thanks
Eric
Subject: Private view and @dbcolumn
You cannot use @DbColumn in views. (And that’s explicitly stated in the Help for that formula)
Subject: Private view and @dbcolumn
I don’t think he’s using @dbColumn in the view - however he may be referencing it in a formula.
The problem that you are encountering in this and in your previous embedded view issue is that Private views are just that: Private. Thay are not intended for “Public” use.
For instance my instinct says for an embedded view to work, all users must have access to it - ie it must be public.
For @dbcolumn, the authority under which the formula is running (generally a user) must have access to that view - ie it must be public. They sometimes will also fail when a view is in fact public but restricted by other view properties from the user.
I believe that private views are stored locally on the system of the user to whom it is designated. They are not stored on the server. Therefore, the server will not create the index because it has nothing to reference it to once its created.
This info is based on my experience. I am not an authority on this in any way.
Subject: RE: Private view and @dbcolumn
Jon,Good call. You’re absolutely correct, private views are just that, private on the local client machine, hence, the server does not have any permissions locally on that client machine.
Regards,
Jan