AccessBlog.net

News, links, downloads, tips and tricks on Microsoft Access and related

About Me Search
Alex
Name:Alex Dybenko

Location:Moscow, Russia

Thursday, July 16, 2015

July 2015 Access updates

July 14, 2015, update for Access 2013

Fixes the following issues:

- When you open multiple objects in design view and then try to switch to another view in Access 2013, Access 2013 may become unresponsive.

- When you undo a column deletion operation in table design view in Access 2013, Access 2013 crashes.

- The Conditional Formatting button does not work if the ribbon is collapsed in Access 2013.

- After you import a form or report or you copy and paste an existing form or report in an Access app, the theme colors are changed unexpectedly under the control of the newly created form or report.

July 14, 2015, update for Access 2010

Fixes the following issue:

When you start Microsoft Access 2010 on a computer that has not been restarted for a long time (for example, 24 days), the CPU usage of the MSACCESS.EXE process becomes high. However, applying this update will reintroduce the problem that is addressed by the hotfix KB2899528 for Access 2010 November 11, 2014. As soon as this update is installed, fields that are bound to expressions on forms may not be recalculated when the computer has not been restarted for a long time.

Labels:

Friday, June 19, 2015

Office 2016 Preview

There is a great opportunity to join Office 2016 Preview program, so you can learn and try its new features!

Labels:

Thursday, June 11, 2015

How To Migrate Data from Desktop to Access App

Tutorial video from Crystal, Access MVP, helps you to understand migration process to Access App, if you never done this before.

 

Labels:

Wednesday, June 03, 2015

ADP+ framework for Access

Missed ADP projects? ADP+ can help you. this is a Data Access Layer for updatable form and subform and for report and subreport to have a client-server rapid ap­pli­ca­tion deve­lop­ment framework in Ac­cess 2013 connected to a SQL Server da­ta­ba­se 7.0, 2000, 2005, 2008, 2012, 2014 and the forthcoming SQL Server 2016.

Labels: ,

Friday, February 20, 2015

Using WMI

Normally we are using Windows API to access registry, etc. You can a lot of tasks with WMI. The main advantage, as I see, that WMI code works with any Windows version, also 32 and 64 bit, so you don't need to use conditional compilation. Hope it will work on future Windows versions as well…

Here a lot of sample code on how to use WMI for different tasks:

WMI Tasks for Scripts and Applications

Labels:

Friday, February 06, 2015

Few FMS papers for SQL Server and upsizing

Worth reading:

Microsoft SQL Server Express: Version Comparison Matrix and Free Downloads

For the first time, all the different versions of SQL Server Express from 2005 to 2014 are shown, compared, and referenced with download links. I can’t even begin to share how time consuming it was to put this together and go through all the details of which O/S each version supports. Just because Microsoft web pages list the versions they support don’t necessarily mean it works when you actually try to install it. I’m sure there are still some minor inaccuracies among the SP releases. Let me know if you’ve experienced something different from what we’ve listed.

Automating the Backup of Your Microsoft SQL Server Express Databases

If you’re using SQL Server Express, you still need to create backups of the database. Here’s how to automate it which wasn’t easy to discover.

When and How to Upsize Microsoft Access Databases to SQL Server

The original version of this was written when Microsoft selected us to do a joint Access to SQL Server Upsizing campaign a decade ago. I’ve updated it to better explain why and why not people should upsize their Access databases and an overview of what the options are and what to do.

Microsoft Access to SQL Server Upsizing Resource Center

Our new Upsizing site with links to our whitepapers and Microsoft resources that help with the whole upsizing process and use of SQL Server Express.

Labels: ,

Wednesday, January 28, 2015

Getting localized NT AUTHORITY domain name

If you are dealing with built-in system accounts, like NT AUTHORITY\SYSTEM, this code can help you on localized Windows versions, where NT AUTHORITY domain is also translated, for example to NT-AUTORITÄT in German version. You can get localized name using it SID "S-1-5-18":

?GetObject("winmgmts:root\cimv2").Get("Win32_SID.SID='S-1-5-18'").ReferencedDomainName

You have to use this function, when you select system object using Object selection dialog as well.

Labels: ,