John W. Colby
jcolby at ColbyConsulting.com
Fri Apr 11 12:33:28 CDT 2003
Folks, I have an instance where I want to hide a rather complex form instead of closing it - to eliminate the load time. The user runs a "filter" form which allows them to select a set of clients / claims, select one, then "open" the claim form. they do this dozens of times a day. By hiding the claim form instead of closing it when they are done, I eliminate the load time which is significant. Basically, the form loads with all claims loaded, then filters down to one specific claim when "opened" from the filter form - literally a filter is applied to the claim form after opening. Applying this filter to an already open form in XP works correctly, the form filters to the new record. Doing so in A2K does not remove the filter. I vaguely remember running into this a year or more ago - having to set the AllowFilter property to no, then back to yes or something similarly obscure. Has anyone seen this and do you have the answer to how to make this work in A2K? Also, this is obviously an A2K problem, so how do I sense that this is an A2K FE so that I don't apply the fix to an AXP FE unnecessarily? John W. Colby Colby Consulting www.ColbyConsulting.com ---------------------------------------------------- Is email taking over your day? Manage your time with eMailBoss. Try it free! http://www.eMailBoss.com