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
> Proof Of Life In Access
Posted by GroverParkGeorge - Sep-7-16 - 0 replies
The A-Team (i.e. the Access development team) at Microsoft have done something which seems to be unprecedented.

For the first time we are aware of, they've started putting their plans for MS Access on the Office 365 Roadmap. You can read more about it on Anders Ebro's (also known as the SmileyCoder) Blog: Smiley Coder's Review of the Office 365 Roadmap for ACCESS.

You can find the Access part of Roadmap itself: Roadmap for Future Access Enhancements

Note that the two items mentioned here have been the subject of considerable discussion among the Microsoft Access MVP Group for a long time, and the topic of active debate on the Microsoft Answers forum and in Access User Voice. The fact that The A-Team is moving ahead on these first two initiatives sends a powerful message to the many fans of our lovable little database tool.

The inclusion of the BigInt data type increases the compatibility between Access and modern versions of SQL Server. That's a good thing from any perspective.

Restoring the ability to link Access to .dbf format files addresses a HUGE pain point for a couple of industries. Most of us probably shrugged our shoulders when it was deprecated in Access 2013, but to those people who NEED this ability, it was a deal-breaker in upgrading to the newer version of Access.

We couldn't be more delighted to see a public announcement regarding Access as it is proof of the A-Team's commitment to keeping Access strong.
Read 3098 times - Reply   print fwd
> Raise A Glass To Doug Steele
Posted by argeedblu - Aug-30-16 - 26 replies
Doug Steele, UA VIP, Microsoft Access MVP, and published Access author, a UA member since January '07, has just passed the 20,000 post milestone. Since joining UA, Doug has provided valuable help to countless members.

Thanks Doug for being an important member of our community. cheers.gif
Read 4729 times - Reply   print fwd
> Bug(s) In Access 2016
Posted by GroverParkGeorge - Jun-15-16 - 12 replies
At this point, it looks like the bug has been fixed. I checked my Access 2016 (32 bit and 64 bit) installations on Win10. I see the full set of values for number datatypes.
July 1, 2016 @ 7:53PM PDT

Job well done, Access Team.

There is a bug in Access 2016. The MS Access team is aware of it, and is working on a fix for it. No ETA yet on when it will be available.

It involves the Datatype dropdown for Numbers.

Only the default datatype is available.

If you need to change or add number fields, the work around is to go to Options for Object Designers and change the Default Datatype for numbers to the one you need. It then becomes available in the dropdown in place of Long Integer.

There have been some reports that Wizards may also be broken. That, however, hasn't been widely confirmed.

ScottGem, Access MVP and UA VIP, is in contact with the Access development team and will let us know as soon as he gets any update.

Update regarding this bug

UA Admin Team
Read 8228 times - Reply   print fwd
> Recommended sites and books
Access Team BlogMicrosoft Access Small Business Solutions
Access Dev CenterProfessional Access 2013 Programming
Access 2013 Inside Out
> Online
1015 users active in the past 60 minutes
Active Users984 guests, 31 members
17pj, admantx.com, ahrefs.com, Alan_G, Archive.org, bing.com, brandwatch.net, carol111, CarrieR, cheekybuddha, Corky, CyberCow, Dan Dungan, DemoMSAC, dmhzx, Doug Steele, ecovindaloo, Everettc4, FVMarketing, gemmathehusky, Google.com, grapeshot.co.uk, halefamily104, ITdarkside, jhcarrell, JonSmith, jriley, MadPiet, mike60smart, MrHans, netseer.com, nfrosa01, nvogel, payfast8898, projecttoday, proximic.com, rgswan, ScottGem, twands8912, webmeup-crawler.com, yandex.com, zinga
Custom Search
RSSSearch   Top   Lo-Fi    20th October 2016 - 04:18 PM