I avoid remote views. They get slow because they spend alot of time assuring that the remote client is getting the "latest" updates. There might be some stuff you could do with a REFRESH setting.

Have you considered using passthrough? Using SQLEXEC() to build a client cursor and then populate your lists with the contents of that cursor?

If they control is expecting data (requery or refresh?) and the data is slow in coming, then it may behave as if it is disabled. Are the other controls on the form working while the combo is "disabled"?


>Here is the refresh() code:
>
>IF NOT EMPTY(THIS.ControlSource) AND THIS.style = 0 && Combo Dropdown
> STORE EVAL(THIS.ControlSource) TO ;
> THIS.Value,THIS.Displayvalue
> NODEFAULT
>ELSE
> DODEFAULT()
>ENDIF
>
>How could the above cause the control to be disabled? Yes, this only seems to happen with Remote SQL Views.
>
>bob
>
>>Could the dropdowns refresh method be the culprit? Is the dropdown associated with a SQL Table?
>>
>>>I have something weird going on and can't figure out what's happening.
>>>
>>>I have forms that are connected to a view to SQL Server, these forms have all types of controls on them, including a Drop Down Box.
>>>
>>>Once in a while the drop down box gets disabled, but none of the other controls, and only when the drop down is setup as a Drop Down Combo, but never as a Drop Down List.
>>>
>>>I can't seem to see a patern, but I'm sure there is one. The view does occasionally have no records, and then is requeried and new records are added, but why would the behavior be different between a Combo/List?
>>>
>>>Any help would be really appreciated.
>>>
>>>Bob