Bruen, Bruce
Bruce.Bruen at railcorp.nsw.gov.au
Tue Dec 6 17:15:38 CST 2005
Then you must avoid at all costs the .Net documentation. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com Sent: Wednesday, 7 December 2005 9:53 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] [Spam] Re: [Spam] Re: [Spam] Re:WhyChangeFieldSi ze/wasCha nge FieldS ize ROTFLMAO!!!! Couldn't agree more! Though I'm sure some of my posts may be the same way. For me, I know why I 'wander' a bit. I tend to learn 'relationally'. So when I understand one set of rules, the next set of rules are learned within the original framework. As new things are learned, it's applied globally. So when I describe how to do something, I tend to wander through the 'relationships' a bit, to try and provide the same background that I used to learn the process. I hate solutions like this: To do XYZ: Type ZYX What I love are solutions like this: To do XYZ, X is something or other, and the process to get to Y involves This or That (click here for information about This or That). Z is then reached by the ABC process. (Click here for ABC process information). Example: Type ZYX When something is explained like that, it not only provides you a solution to what you are looking for, but also allows you to extrapolate other similar solutions, or even fine tune the example to better bit your needs. Solutions which don't explain the process involved, or don't provide an working example, IMHO are just plain incomplete, and far less useful then a complete solution. One of the reasons I LOVE Access 97's help file. Drew -----Original Message----- From: William Hindman [mailto:wdhindman at bellsouth.net] Sent: Tuesday, December 06, 2005 4:37 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] [Spam] Re: [Spam] Re: [Spam] Re: WhyChangeFieldSi ze/wasCha nge FieldS ize ...rather more obtuse than ambiguous :) <etc> This e-mail and any attachments may contain confidential information that is intended solely for the use of the intended recipient and may be subject to copyright. If you receive this e-mail in error, please notify the sender immediately and delete the e-mail and its attachments from your system. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. Any opinion expressed in this e-mail and any attachments is not an opinion of RailCorp unless stated or apparent from its content. RailCorp is not responsible for any unauthorised alterations to this e-mail or any attachments. RailCorp will not incur any liability resulting directly or indirectly as a result of the recipient accessing any of the attached files that may contain a virus.