Denis Sherman
max.wanadoo at gmail.com
Wed Feb 25 01:44:34 CST 2009
>> There is a generic property (limited to 2048 characters, by the way), which can be used for anything...and can be used by anything. But using it for multiple purposes gets to be very hairy! However, I was just playing around with user-defined-properties in the mdb properties itself - for storing these multi-value strings each formname+controlname to have its own user defined property name with the value being the multi-value language string. Worked beautifully apart from the limitation around the 64K size mark. I have another plan - just thinking it through laterally first! Max -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: 24 February 2009 22:58 To: Access Developers discussion and problem solving Subject: Re: [AccessD] Find First in an Array? - The Solution Revisited -Now Tag is the Answer Not quite. 1. Need to have multiple values for a single value property for the controls. 2. There is a generic property (limited to 2048 characters, by the way), which can be used for anything...and can be used by anything. But using it for multiple purposes gets to be very hairy! 3. It took me less then 30 minutes to build a completely new system that does the same thing, just as fast, and it is event enabled (ie, changing the language on the fly updates ALL visible forms (and I'm assuming reports...) to the new language. Something you can't do as easily with the Tag. I'm not saying that using the .Tag property would be bad. I just think a class/collection method is better. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Tuesday, February 24, 2009 4:27 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Find First in an Array? - The Solution Revisited -Now Tag is the Answer So let me get this clear. Your argument is: 1. I need to store a string value for each control. 2. Controls has been designed with a property specifically for this purpose. 3. I won't use the property in case I need to use it for something else later on, instead I will build a complete new system which will allow me to do all sorts of neat things with controls in case I need to in the future. May I refer you to Shamil's posting last Friday in this thread? <quote> May I warn you about what is known as: "Premature Optimization" http://c2.com/cgi/wiki?PrematureOptimization and "Premature Generalization" http://c2.com/cgi/wiki?PrematureGeneralizationIsEvil Have a look: "Death by premature generalization" http://ryanfarley.com/blog/archive/2004/04/30/570.aspx </quote> -- Stuart The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com