UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
> Microsoft Access Help Forums
The premier Microsoft Access help forum with Visual Basic, SQL Server, Office and more! Members are able to post questions and help others with problem solutions. UtterAccess has been seen in over 160 countries, recording over one billion hits to date. Microsoft Access Tables, Queries, Forms, Reports, Pages, Macros, Modules...you'll find all the free samples and answers here!

Registered members have access to all the file attachments that UA is pleased to provide. An added bonus along with many other features such as Access sample databases, professional Access code samples, file uploading, private messaging and forum subscriptions...all this for those who take a moment to sign up...(Your personal information is kept completely confidential and everything is truly free of charge!)

Over 250,000 members have signed up at UA to enjoy well over 2,500,000 posts - proving UtterAccess.com is the only source for help with Microsoft Access...and more!
> Additional UA Navigation
Discussion ForumsCode Archive Table of ContentsThe Microsoft Access WikiNewcomer's Reading List
Today's Active TopicsHow to post a good questionContact UADifferences in Access Versions
> A Heads Up To Anyone Using Access With A SQL Server Back End
Posted by GroverParkGeorge - Jan-16-20 - 9 replies
A new Access bug, apparently related to the recent update for version 1912 of Office (out since January 8th, 2020) can result in Access failing to recognize Identity Insert on AutoNumber fields , rendering them as Long Integer Numbers (not AutoNumber) in Linked Tables in Access. Details are emerging. However, if you experience problems with linking/relinking tables correctly, or using Recordset.Bookmark to retrieve a newly inserted Primary Key in VBA, please share your experiences so we can more fully update the Microsoft Access team.

Update: Microsoft posts an official notice: https://support.office.com/en-us/article/ac...f1-7e043812d60d

Thank you.
Read 561 times - Reply   print fwd
> UtterAccess In The 2020 Decade
Posted by jleach - Jan-6-20 - 6 replies
It's hard to believe that UtterAccess is in it's 18th year now. Created in 2002 (April 27th, to be exact, when Gord launched it), UA has been a home to myself and many others for a long, long time. The origins of UA go back even further... Simon Wolf and A3 (Access All Areas) preceded UA, and A3 was born somewhere between January 1999 (the furthest public record of the site we can find), and January 2000 when it became "official." Going back just a bit further, Simon once spoke of how even A3 came to be: his decision to host his own website around March of 1997, which included Access-based content that began to collect a following of interested people that drove the evolution to UA today. That's 23 years...

Twenty. Three. Years. For a free, public, community-driven website. notworthy.gif

It's almost as impressive as the tenure of Access itself.

Therefore, it is immensely gratifying to be able to write this to announce that we're nowhere near done.

We have a number of plans for UA in the year 2020 and forward. Some of this is already heavily underway in the background, while some things are tentative and still in vague idea stages, but in either case we're excited to announce a number of upcoming changes.


New Forum Software
Most notably, UA will be undergoing a software change. The current software was implemented for specific reasons at the time, yet comes with some difficulties in providing updates to the software. Now, years later, we've moved on from those specific reasons and are more interested in the ability to improve UA moving forward.

In mid-2019, we started taking a hard look at what to do with UA's software situation. Continue with the current implementation? Find something off the shelf? Write something from scratch? The answers of course depend on where we want to be in the future, and what kind of path we want to take to get there.

We don't feel that continuing with the current software is a wise long-term forward path. While it's served its purpose quite well, it is difficult to manage and based on what's considered antiquated technology in modern day web applications. We looked at other 3rd party software as well, though there's really only one (discourse.org) that is any "better" or "more modern" than what UA already is. While it likely would have been easier to adopt discourse as a new platform for UA, it wouldn't help us in terms of having our own flexible software to ride the future with.

Ultimately, we decided that a new custom developed software fits the needs well and offers the easiest forward path for many of the future plans for UA. As such, a new version of UA has been in development since September of 2019, and we expect the following timeline for it's major public milestones:

- End of First Quarter 2020: public beta release of the new "UAv4" web application
- End of Second Quarter 2020: final move to the new UAv4 software and retirement of the current software

What to expect?

- All existing content to be retained
- All existing memberships to be retained
- All existing messages, avatars, uploads and such to be retained
- The greater majority of current forum software features to be retained
- A number of new features, many of which will be related to ease of posting and searching
- UA "Areas" (discussed in more detail below)

We've been working with the UA VIPs on feature suggestions/discussion and have collected a number of requests from the public suggestion forums and included these in our considerations for feature priorities in the new software. While we can't promise that every suggestion/request will be implemented, we think the UA membership on the whole will be pleased with the new software, and we have plans to set up a more formal feedback/feature request mechanism for future requests.


UtterAccess Areas
A significant factor in our decision to undertake the UAv4 custom software project is that we want to be able to expand UA beyond only forums. We feel that there's a great number of ways that UA can serve the Access community, and that forum discussion is one of many ways to do so. Over the years, we've supported some of these things through the existing forum interface, but we believe that there's better ways of doing so.

As such, with the UAv4 software, we've allowed for varying "Areas" that can be added to UA. An Area can be thought of as a major chunk of functionality, or perhaps as a sub-site or differing feature set. The forum itself will be one (the main) Area, and members can participle/visit only that Area if they prefer not to be involved in others.

While the timeline above for the UAv4 software only covers the core Forum Area, here are some examples of things we may (or may not...) implement as separate Areas in the future:

- A dedicated Area for articles/documentation (like the wiki)
- An Area for the Code Archive (this can include discussion, but can be presented differently, not in forum-first mode as it currently is)
- An Area for job postings (potentially: we could, but haven't decided yet if we will)
- Potentially Areas for other development platforms (.NET, BI, AI/ML, etc)
- Tool and product catalog/search/comparisons

These are examples of things that could be done, and the key takeaway is that each Area can essentially be a separate web application custom-built to support the content, rather than trying to fit that content into a forum software's box.

As part of the UAv4 software, we've specifically designed the overall system architecture to support any number of future Areas that we may want to implement.


Wiki, Code Archive, FAQs and Knowledgebase(s)
While the initial release of the UAv4 software will have only the core Forum Area, we have concrete plans to move certain types of content currently within the forums to a new Area for articles/documentation/faqs and such.

Also, there's a question of what happens with the UA Wiki.

The Wiki was a large undertaking (and is the reason for the current software: integration between forum and wiki), and while initially there was a lot of content added and the articles still get a number of views to date, it has been mostly inactive in terms of contributions in recent years. Rather than trying to continue running the wiki in conjunction with the UAv4 software (the two are on completely different development platforms), we will be "freezing" the wiki as read-only, retaining the content, and eventually migrating it to the future planned Articles Area.

Along with the wiki being moved to a new Articles Area, there's a number of various FAQs and knowledgebase-type topics/boards currently in UA that we feel can be better utilized in a dedicated Articles area. We will begin moving this content to the new Area when ready.


Mobile App
While the UAv4's UI/UX will offer some improvement for smaller form-factors (e.g., a bit more tablet friendly), it's pretty much a hard fact that the UA site is mostly a desktop experience and should stay that way.

With that said, we do have plans for an initial basic mobile app to be released by the end of 2020 for Apple and Android devices. The initial release of this will cover basic forum interactions in a feature-light manner.


Over and out
We'd like to take this opportunity to offer some thanks to everyone who has been a part of the UtterAccess community and Access community at large. Specifically, our founding fathers Simon Wolf and Gord Hubbell, as well as a number of the "original team" core administration (Jerry Dennison, Ricky Hicks), and many of the long-time administration members since the early days of UA (Glen Kruger especially, Mark Davis, DougY, George Hepworth, and a host of others who I won't list out completely).

Looking forward to the next 20 years thumbup.gif
Read 615 times - Reply   print fwd
> Reminder: Access User Voice
Posted by GroverParkGeorge - Dec-21-19 - 8 replies
One of the most important tools available to Microsoft Access developers is the Access User Voice forum. In addition to a link to Current Fixes and Workarounds for Recent Issues in Access, User Voice provides a way for us to submit requests for enhancements to our favorite Relational Database Development Tool directly to Microsoft.

We suggest you visit User Voice regularly and either submit your own ideas, or give your support to existing requests.

Note: this is not a place to make complaints or criticisms, or to ask about specific problems in your own Access Relational Database Applications.


One recent example of an idea that makes a lot of sense for us these days is the request to support Large Address Awareness for 32 bit Access. Many of us have experienced problems with memory and resource limitations when working with more complex Access Relational Database Applications. Each new version seems to be more susceptible to the problem. Making LAA the default for Access would be a big help.

You can find this, and many other great ideas, at Access User Voice. Please take time to review what is there and participate in the discussion.
Read 1396 times - Reply   print fwd
> Recommended sites and books
SitesBooks
Access Team BlogMicrosoft Access Small Business Solutions
Access Dev CenterProfessional Access 2013 Programming
Access 2013 Inside Out
> Online
889 users active in the past 60 minutes
Active Users879 guests, 10 members
ahrefs.com, bing.com, Brabee, brandwatch.net, CASCPA, drakopp, facebook.com, Google.com, grapeshot.co.uk, June7, kamellias, lpeter1632, ollyhutsy, pacof4, proximic.com, sajadssa, Vince, yandex.com
Custom Search


RSSSearch   Top   Lo-Fi    24th January 2020 - 03:00 AM