[AccessD] Office 2010

[Darryl Collins]

Agreed. You should do it this way anyway.  Being as explicit as necessary with variables can save you from flaky behaviour and crashes.



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Thursday, 5 November 2015 7:59 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Office 2010

Explicitly identifying Recordset as DAO is a good idea.  Makes the code more maintainable down the line and avoids unintended conflicts.

I would do a global replace on "AS Recordset" with "AS DAO.Recordset" with the option to Replace or Find Next - couldn't take very long, could it?

Rocky


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kaup, Chester
Sent: Wednesday, November 04, 2015 12:28 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Office 2010

My office computer recently got upgraded from Office 2007 to Office 2010. In my database in the code module I have Dim mydb as DAO database. Office 2010 seems to want me to put DAO in front of every recordset dim statement. EX Dim RS1 as DAO.Recordset. Is there a better way than having to do this for the entire database?

Also since the calendar control no longer exists what is a good solution?

Thank you for your thoughts.
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com