developer
197 TopicsMoving Away from MS Access
The organization I work for is wanting to move away from Microsoft Access databases where possible, and we have started exploring what tools our current Access databases could be moved to. Is there a standard for what works best (Powerapps, Sharepoint, etc)? What have you found to be a good resource for guidance on this topic? Thanks!126KViews2likes81CommentsAccess doesn't close properly. A remaining background process can only be terminated in task manager
Since yesterday I noticed that in all my Access databases there is a problem when I close them. When I close a database, it leaves a background process that can only be terminated in Task Manager. Without this, it is not possible to (re)open databases! I have already checked some possible causes. It also concerns databases that I have not changed at all in recent months and that worked fine until this week. Therefore, I have to assume that it is a bug in an automatic update! It seems that it has to do with a malfunction in the deallocation of allocated memory in VBA source code. Did anyone experience the same problem? Are there already fixes or solutions available?Solved92KViews8likes189CommentsMicrosoft Access Version Comparison Matrix
Microsoft Access debuted in 1992 and recently celebrated its 25th Anniversary! Over the decades, Microsoft Access evolved with a large number of enhancements, database formats, and discontinued features. It's hard to remember all the changes. We created a page that shows the different Microsoft Access versions and changes in an easy to understand comparison matrix. Microsoft Access Version Features and Differences Comparison Matrix See when versions were released, their latest service packs, database formats, linked tables, field types, security features, Windows Operating Systems, and many other features both new and old. Hope this helps. Let us know if we missed anything.Solved30KViews13likes13CommentsFuture of Microsoft Access: PowerApps|CDS|VSTO|VBA|Flow|JS|VS|.NET|Graph Cloud|Mobile|Web|Developers
Access & Office Development Roadmap & Suggestions In addition to summing up recent Access updates & resources (including those from Access), I've compiled some suggestions & questions for the Access & Office Dev Platform teams (ranging from PowerApps & Common Data Service integration to VSTO Add-in dev, VBA & VBE) here. I've also recapped the recent Microsoft reorg changes along with thoughts on potential implications for Access & Office. Also, if at all possible, any glimpse the Microsoft Access and Office Developer Platform (VBA, VBE IDE, Office.js, VSTO) teams could provide us with into what they are considering (even if not confirmed yet) as possible future enhancements, fixes and data connectors for Access and improvements for Access developers (automation/macros/add-in development) for Access 2019 / Office 2019 (http://www.codekabinett.com/rdumps.php?Lang=2&targetDoc=office-access-2019-news) onward would be greatly appreciated. Promising Trend of Access Updates vs. Cloud-first Focus & Dropped Web Support Considering, on one hand, the number of promising recent Access updates (summarized below, per Access Day) and, on the other, the deprecation of Access Web Apps (AWA & Access Services for Microsoft-hosted SharePoint Online going read-only by April 2 '18) and Microsoft's recent Cloud-first focus (PowerApps, Common Data Service, Azure) and Cloud vs. UX reorg. shakeup. Microsoft Reorganization (Cloud vs UX Shakeup) Implications Also, I'm wondering if anyone has any thoughts on possible implications of the just-announced http://www.zdnet.com/article/heres-how-and-why-microsoft-is-splitting-up-windows-in-its-latest-reorg/ on Access, Office development and Microsoft Office / Office 365 in general. Specifically, as I will detail in my next post, Microsoft has combined their 4 groups into just two groups, essentially splitting by Cloud vs. non-Cloud - a "Cloud & AI" group, including Azure, PowerApps, Power BI, Dev Tools/APIs, among other things vs. a "Devices & User Experience" group, including Office, Windows, Surface & Mobile. Recent Access Features & Updates I'd like to start off by recapping all the recent advancements we've seen with Microsoft Access, at Access Day and beyond. Considering all the http://www.fmsinc.com/microsoftaccess/history/features.htm and toying with removal of Access from most Office editions, it's really great to see that Microsoft ended up (after the user backlash) https://twitter.com/PowerAccessSQL/status/974477100521525248 instead! More than that, its really incredible to see all the new Access updates, such as new Data Connectors (Microsoft Dynamics & Salesforce), https://blogs.office.com/en-us/2017/03/06/new-in-access-2016-large-number-bigint-support/ support, an upcoming https://blogs.office.com/en-us/2016/09/07/back-by-popular-demand-dbase-file-support-in-access/, https://support.office.com/en-us/article/featured-access-templates-e14f25e4-78b6-41de-8278-1afcfc91a9cb?ui=en-US&rs=en-US&ad=US (experimentally) and 32-bit SSMA release (with the SQL Server Migration Assistant for Access previously only usable with uncommon 64-bit Office installs). Also, I'm glad to see the Access Accessibility Updates (Screen reader, F6 navigation, high contrast, etc.), which even as I understand, helped lead to Microsoft receiving the https://blogs.microsoft.com/firehose/2017/09/07/microsoft-recognized-for-leadership-in-bringing-inclusion-to-product-design/ for tech enabling the over 1 Billion across the world with disabilities. Congrats to the Access, Office and Accessibility teams on that achievement! Access Team's Support & Updates I also very much appreciate the new content and support from the Access team. For those not familiar with all of it, that includes new resources under and https://support.office.com/en-us/access with https://developer.microsoft.com/en-us/access/docs and https://support.office.com/en-us/article/access-video-training-a5ffb1ef-4cc4-4d79-a862-e2dda6ef38e6, as well as https://support.office.com/en-us/article/featured-access-templates-e14f25e4-78b6-41de-8278-1afcfc91a9cb?ui=en-US&rs=en-US&ad=US and the attention the Access dev team is providing to https://access.uservoice.com/ and https://officespdev.uservoice.com/, as well as all the activity in the the new Access blog and Access forums here. Upcoming Features for Access and Access Day Revelations I was exciting hearing about the upcoming support for New Chart types and R2 update of https://www.microsoft.com/en-us/download/details.aspx?id=54920, all covered at http://jstreettech.com/RedmondWA2018Schedule.aspx by Access Program Manager Michal_Bar, as seen in her https://www.facebook.com/JStreetTech/videos/1871973549481976/ (thanks to ArmenS and his post on the new charts). Access Dropped from Visual Studio Tools for Office (VSTO) for .NET Add-in Development However, there are a few things long-missing or rarely updated which I would love to see to simplify life for Access developers and enable better integration with or taking advantage of the latest, Cloud-focused Microsoft product and developer tool/API advancements. For example, I, and many others https://www.linkedin.com/feed/update/urn:li:activity:6331932689293279232/, would really like to see at least Access supported with https://msdn.microsoft.com/en-us/library/ms268878.aspx for add-in development again, as well as modernizing development tools/APIs for macros/automation. Specifically, it would be great if at some point in the future we could see updates to the VBE / VBA IDE (eg. adding tabbed documents, both forward/backward edit navigation, etc. as missing most VS updates since forked from VS around VB6), updates to VBA language (which hasn't seen much in the way of updates since VB6 it was based on), Visual Studio use for VBA (for macro coding, debugging & edit-and-continue), Microsoft Flow automation (eg. using On-premises Data Gateway or VPN connection or OneDrive), Office.js API, and/or VB.NET / C# / .NET for macro coding. VBE (VBA IDE) Issues There are also long-standing issues with VBE (VBA IDE) like it being unable to handle multiple monitors with different resolutions without ghosting when resizing tool panels. And missing modern text editor features (let alone modern Visual Studio features) like Tabbed Documents, Forward & Backwards edit navigation/history, etc. We ended up seeing and dealing with this for example (in addition to encountering it all the time myself) even during the presentations at Access Day. Automation (Macro & Add-in Development) API Limitations For Add-in developers and VBA Macro/Automation developers, Access could really benefit IMO from adding events, like for OnAppExit, OnSave globally and for each object/window, access to multiple objects selected in Navigation Sidebar, defining hotkeys via code (vs AutoKeys), extend the Nav sidebar context menu - to name a few. I will likely post a compiled list of suggestions later on regarding Access and VBA/VBE Automation APIs. Documentation & Samples Missing However, developer docs and content is completely missing for Access from https://developer.microsoft.com/en-us/office/gallery/?filterBy=Samples,Access and https://dev.office.com/training, and https://products.office.com/en-US/business/office-365-roadmap?filters=access (which only has 3 entries for Access: Salesforce + BigInt as completed, and Dynamics 365 connector shown as still WIP/Still Rolling Out) as well as https://docs.microsoft.com/en-us/office/dev/add-ins/, https://msdn.microsoft.com/en-us/library/23cw517s.aspx and https://docs.microsoft.com/en-us/visualstudio/ide/creating-project-and-item-templates. Content missing from those last three places is likely due to Access being dropped entirely from VSTO for some reason, but even then there are other ways (eg. COM APIs, 3rd party wrappers, etc.) that could at least be mentioned there, or even include older VSTO docs. People are developing add-ins with Access, regardless of it being dropped from VSTO, but there is no documentation on how to do that. Making the Access Templates Experiment Permanent Also, Access Templates should definitely be kept permanently and shown to everyone all the time. As Michal had pointed out, Access Templates end up being shown randomly (for A/B testing) just for some users on https://templates.office.com/. However, after refreshing 2 dozen times, trying with a dozen Incognito sessions across several dozen sessions it took dozens of attempts to finally see it, so I'm not sure it's shown as often may be though. Cloud Data Connectors (Common Data Service and Graph) like Excel & other Office Apps Similarly, I would love to see https://docs.microsoft.com/en-us/common-data-service/ and https://developer.microsoft.com/en-us/graph support (and maybe direct access to Power BI-embedded data) in Microsoft Access. As Juan Soto had pointed out, Excel and other Office and MS apps provide Common Data Service support, with just Microsoft Access as the one missing out. Access Web App "Replacement" PowerApps Supports Everything Except Access For other improvements beyond Access/Excel/Office Macros and Developer Tools/API, I'd really think it valuable for https://powerapps.microsoft.com/en-us/, https://flow.microsoft.com/en-us/, and https://powerbi.microsoft.com/en-us/ Online (beyond just Desktop version, for Service / Premium / Report Server / Mobile / Gateway, and without import Desktop to Service hack) to provide direct support for Access databases. On-premises Data Gateway: Possibility for Using Access from PowerApps & Power BI for Web & Mobile It's frustrating not even being able to setup the https://docs.microsoft.com/en-us/power-bi/service-gateway-onprem (installed on local PC for "File System" access, shared by PowerApps and Power BI) to support Access databases in PowerApps - just Excel workbooks. Concerns Regarding Microsoft Priorities for Azure & PowerApps vs. Access However, considering how even Access Services (for SharePoint-Access integration via Access Web Apps (AWA) as well as earlier Access Web Databases) being deprecated and going read-only (April 1, 2018), I wonder how likely that might be that we get further Cloud/Web/Mobile features. Considering this and how Microsoft attempted to even remove Access from most Office editions recently, as well as their Cloud-first focus, it's a bit concerning. It seems like with Access being included in Office there is a lot less revenue to be made from it compared to billing monthly (and by usage) with PowerApps, Power BI, Azure, etc. I can understand Microsoft's business priorities there, but, considering Access is often used for prototyping databases for SQL Server and Azure SQL, as well as quick, end-user-editable front-ends for them, I think it would make more sense IMO to expand Access' integration with Azure and Cloud Services versus trying to drop it from Office editions and replace with PowerApps which can't even connect to Access (pushing use of Excel spreadsheets for data storage and queries instead, for file system connectors). There is little-to-no support for even connecting to Access Databases from PowerApps and Power BI and even OneDrive/Dropbox deployment not being feasible (unlike Excel, now with its real-time multi-user collaborative desktop editing enabled when deployed that way, let alone Excel Online deployment). Remaining Deployment Options: VPN File Shares & Remote Access (RDP, RemoteApps, Citrix) Considering this, the we are limited for multi-user deployment to Network Shares over VPN (not feasible if want clients or customers to be able to use, or access from home for many) and Remote Desktop (RDP - though RemoteApp is a pretty good option), or Citrix & other RDP-like options (now that Azure RemoteApp hosting is deprecated). Questions for Access & Office Dev Platform Teams To sum up, my primary questions (and suggestions) for the Access development team are the following: Is there any chance we may see Microsoft Access integration with PowerApps, Common Data Service, Azure, Microsoft Graph, Power BI Online, SharePoint, Office Online, On-premises Data Gateway, OneDrive, Dropbox and/or Microsoft Flow? Any other possibilities to simplify Web, Mobile, Cloud Drive (eg. making OneDrive feasible to use, like with Excel for multi-users), or otherwise simplifying Multi-User use and deployment for Microsoft Access? Is there any chance we could get Access added back to Visual Studio Tools for Office (VSTO) for officially supported and documented (complete with Visual Studio project templates) for .NET Add-in development for Access, like with Excel and other office apps? Any possibility of updates to VBA, VBE IDE, or support for Visual Studio for VBA or C#/VB.NET for macro coding, or JavaScript (eg. Office.js), or even Microsoft Flow (eg. via Gateway, VPN, or OneDrive) for automation?Solved27KViews6likes6CommentsUsername from Office-Account with VBA (Access2016)?
I want to read the username of the current logged in Office account in MS Access 2016 with VBA (not Windows or network username). The logged in user appears indeed in the Office2016 applications respectively in the title bar at the top right. Environ (), etc. unfortunately does not help. As some users have different office accounts (partly for business and / or private) and change between these (eg due to access to your own OneDrive files). I would like the Office-username (account-name) for the user-specific representation of information in forms, queries, etc. I Have already found that the previously registered users will be added to the registry and are thus read, but which of these is the currently logged on? Thanks for your help23KViews7likes9CommentsWelcome to the Access Tech Community!
This is a place to share ideas, news, discuss the product, promote Access events and engage with Access MVPs. In this community you'll also find the Access product blog, where we share updates from the Access team, customer success stories and MVPs articles. If you have technical questions and would like to receive support, we recommend that you visit one of these active Access online forum geared towards support and/or Access development: Microsoft Answers: Answers.com MSDN Access for Developers Forum: MSDN Dev Forum UtterAccess -UtterAccess Stack Overflow: Stack Overflow LinkedIn - Professional Microsoft Access Developers' Network --The Access Team18KViews24likes32CommentsMS Access force a popup on top of other windows?? Is this possible?
I am just wondering if there is a way to have access display a popup form (even just a message saying, "hey you got a new entry by an use!" ON TOP of another window (say, Chrome Explorer, or whatever other windows. Is this possible??13KViews1like4CommentsNumber of simultaneous users allowed to access database
Hi All, So far I have designed access applications for less tha 20 users. Now I have a requirement to develop something wherein users are around 130. I am thinking to develop front end using excel and back end using access database. However I am concerned whether such huge number of users are allowed or not. In total these 130 users will make around 21000 read write operations in a day . Need expert advise over it. Thanks in advance9.4KViews0likes4CommentsProblem Creating a usable zip file using VBA. Does anyone have an alternative?
I am hitting a problem creating a usable zip file using VBA. I am using the following code block to create a zip file. I found it in virtually all internet posts that I came across and for that, I copied it with high confidence that it will work. But it's not working as expected when the storage device is a MicroSD or Flash Drive. the sub-routine works fine if the storage device is an internal hard drive, portable hard drive (HDD) or portable solid-state drive (SSD) sub Create_Zip_File (argDestZipPath as Variant) Open argDestZipPath For Output As #1 'Create an empty zip file Print #1, Chr$(80) & Chr$(75) & Chr$(5) & Chr$(6) & String(18, 0) Close #1 end sub The sub-routine does create an empty zip file on a Flash Drive or MicroSD storage device on the specified path, but I can't open it either manually or with vba code. I get the following prompt as I manually click on the zip file icon in the window or as I attempt to utilize the shell.CopyHere method using the statements below. Set ShellApp = CreateObject("Shell.Application") ShellApp.Namespace(argDestZipPath).CopyHere ShellApp.Namespace(argItemToZipPath) In comparison, I can manually create an empty zip file in the same location on the Flash or MicroSD and can successfully open the resulting file by manually clicking the icon or by way of vba code without incurring the prompt. I can also create the empty zipped file on the hard drive, then move it to the flash drive or MicroSD where it works normally without incurring the prompt. The problem occurs only when the subroutine creates the zip file directly to the FlashDrive or MicroSD. Background I am using Windows 10 (Home), with the most recent updates, and am using MS Access in an Office 365 subscription that I believe is also up to date. I have a 64bit machine. The MicroSD card and flash drive are formatted as NTFS. I suspect there is an alternative to the Print statement that creates the zip file that will configure the zipped file exactly as does the manual procedure available on the windows explorer shortcut menu Does anyone know an alternative to the following? Print #1, Chr$(80) & Chr$(75) & Chr$(5) & Chr$(6) & String(18, 0) My current vba workaround is to automatically create the empty zip file on the hard drive, then move copy (via FileSystemObject class) a pre-existing empty zipfile.zip on the hard drive to the MicroSD or Flash drive, then renaming it according to characteristics of the intended content before proceeding to send files to it. This is effective as a stop-gap but certainly not preferred.8.7KViews1like9Comments