jwcolby
jwcolby at colbyconsulting.com
Thu Nov 1 21:41:07 CDT 2012
>I can't think of a single thing I am using today that I used in 97. uuhhh??? tables, fields, queries, reports, forms? Sure the code (vba) is much better in 2003 but 97 worked. John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 11/1/2012 6:02 PM, William Benson wrote: > Why haven't they upgraded? I can't think of a single thing I am using today > that I used in 97. > > On Thu, Nov 1, 2012 at 5:32 PM, Stuart McLachlan <stuart at lexacorp.com.pg>wrote: > >> One biggie for me is dropping support for Jet 3. "This change affects >> databases that are >> linked to Access 97 databases." >> >> I've got clients with lots of A97 backends. >> >> -- >> Stuart >> >> On 1 Nov 2012 at 15:06, Jim Dettman wrote: >> >>> >> > If you haven't figured it out, we (developers) are not going to be in >> the >>> picture much longer. >>> >>> Microsoft just released details on Office and Access 2013: >>> >>> http://msdn.microsoft.com/en-us/library/jj162978(v=office.15).aspx >>> >>> Couple of quotes: >>> >>> "A new interactive view designer makes it easy for users who have little >> or >>> no programming experience to build apps. " >>> "A new application model enables subject matter experts to quickly create >>> and share applications that can be used to run their business. " >>> >>> They are focused on the end user and nothing but and everything is >> about >>> the cloud and Office 365. Traditional desktop development with Access is >>> out. >>> >>> Here's a list of what got pulled out: >>> >>> >> http://technet.microsoft.com/en-us/library/cc178954%28v=office.15%29.aspx; >>> >>> >>> Two biggies from that: >>> >>> 1. Access 2003 toolbars and command bars are no longer supported. You >>> *must* use the ribbon. >>> 2. ADP's are gone. >>> >>> And there's a bunch of other stuff, like Pivot Charts. >>> >>> Jim. >>> -----Original Message----- >>> From: accessd-bounces at databaseadvisors.com >>> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tina Norris >>> Fields >>> Sent: Thursday, November 01, 2012 02:52 PM >>> To: Access Developers discussion and problem solving >>> Subject: Re: [AccessD] Regarding multi-value field, from a reader >>> >>> Well, for what it's worth, I agree with everybody who said don't use >>> multi-value fields! Geez, we go to lots of trouble to normalize our >>> data and then Access arrives with new specialties that at least look >>> like the destruction of normalization! Dang! >>> T >>> >>> Tina Norris Fields >>> tinanfields at torchlake.com >>> 231-322-2787 >>> >>> On 10/31/2012 7:08 PM, Susan Harkins wrote: >>>> Received the following from a reader: >>>> >>>> "I set up a multivalued field in Access 2010 using a List Box and >>>> providing a Value List with values M,T,W,R,F. Everything works fine >>>> but for one problem. When I chose M, W, F from my list, th >>>> emultivalued filed reads F, M, W ... i.e., the entries are sorted left >>>> to right whereas I want them to show up as M, W, F. Is there a way to >>>> do this?" >>>> >>>> =====Other than learning the basics so I could write about them, I >>>> don't use them and have almost no experience. Anyone have a quick and >>>> easy answer? I'm going to do a little research, but if anybody knows, >>>> please share! >>>> >>>> Thanks! >>>> Susan H. >>> >>> -- >>> AccessD mailing list >>> AccessD at databaseadvisors.com >>> http://databaseadvisors.com/mailman/listinfo/accessd >>> Website: http://www.databaseadvisors.com >>> >>> -- >>> AccessD mailing list >>> AccessD at databaseadvisors.com >>> http://databaseadvisors.com/mailman/listinfo/accessd >>> Website: http://www.databaseadvisors.com >>> >> >> >> -- >> AccessD mailing list >> AccessD at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/accessd >> Website: http://www.databaseadvisors.com >> > > >