John W. Colby
jcolby at ColbyConsulting.com
Sat Apr 12 09:50:19 CDT 2003
Well the fix was simple. The initial form that built up the filter (frmClientSrch) had been setting the Filter property on the actual form that displayed the filtered record (frmResults) to something similar to: "[CL_LName] Like Forms!frmClientSearch!txtLName". Thus if they searched on LName several times in a row, the second and subsequent searches never caused an actual change in the string sent to the Filter property. The fix was to evaluate "Forms!frmClientSearch!txtLName" down to an actual value and send a string that looked like "[CL_LName]like SM*". Thus presumably the next filter would look different - perhaps "[CL_LName]= Col*". Since the actual string placed in the Filter property is different, A2K re-evaluates the filter and displays a different set of records. AXP re-evaluated the filter in both cases so I could sent it "[CL_LName] Like Forms!frmClientSearch!txtLName" over and over and each time it would look back at the frmClientSearch to see what txtLastName looked like. Just thought you might like to know that this difference exists and what I discovered. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby Sent: Friday, April 11, 2003 1:33 PM To: AccessD Subject: [AccessD] Differences - AXP and A2K 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 _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com ---------------------------------------------------- Is email taking over your day? Manage your time with eMailBoss. Try it free! http://www.eMailBoss.com -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 3096 bytes Desc: not available URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030412/4c0f1515/attachment-0001.bin>