Microsoft Access - 2010 Demo | The Access Show

ChrisLinx

Clint -

I just wanted to thank you publicly for taking the time to answer my query. Those links were helpful, too.

Also, I've just returned from Office DevCon 2009 here in Australia and have to say I was impressed by the way Access is heading.

The guys from Redmond were great & our confidence is restored! Yeah, the ribbon's a pain from a developer's perspective but there are ways around it and lots of great features in Access 2010 that we could utilize to have a very slick commercial product.

Thanks for the offer of direct contact - will take you up on it.

Cheers,

Chris

oxMike

Hi, I'm not a full blown developer, more of a power user. The new stuff looks good to me.

However, can we publish to non Sharepoint sites? I for one cannot afford the licence for SP. So I imagine, a lot of others too.

oX.

dyapp

I also refuse to develop a database for users using 2007 for development. Layout and forms design might be little better but the whole UI sucks compared to Access 2003 which is way easier to develop on. Seriously give developers the tools they need to make great databases, not for these people who don't know what a database is from a excel spreadsheet. True databases need strong forms, datatypes like SQL ,Great reports, VBA macros with strong intellisense and data macros.. and it should way easier to create and edit queries, and the SQL editor is not even up to SSMS standards, nor does it have any functionality like Notepad for crying out loud. And why cant Access themes all the controls a certain way, and why cant we write native SQL, why cant VS2005 QBE be included instead of the garbage query creator, and why cannot we create queries like the SSMS app.. and why cannot the navigation bar not be so hard to see the objects, there is too many customized objects view and too large of text, and too big of icons, and no tree like SSMS view of a SQL Server database in VS. And why cannot security be simple to implement like a SQL server access. And why doesn't access have F5 to run querys and why cannot I write a SQL statement in VBA to read data from a table like I would in a query.. why is everything not compatible with TSQL when porting the SQL behind a JET QBE query, and why doesn't the ODBC use a one time security password for the connection and not to all tables.. why do I have to go through so many screens to import a table, and why is VBA not color coded to make our life easier.. and why cannot I reference a table field in VBA by just doing: table.field.value = where record id field = my index number.

All this these so called features in 2010 are for dumb end users who cannot see and are blind and these examples for databases are always like I build a form with a table in design grid, that is my database.. no real develop creates an Access databases that way.. . 2007 only made the end user feel better about using Access. It did absolutely nothing to help developers make better databases or make development of databases easier.. and I agree with the previous comment.. even the import wizard is a piece of crap.. I've tried to import over 40+ different Text and XLS file formats and had to modify most by hand before Access could even import half of them with any type of success rate to get past the wizard.

I need SQL DataTime Stamp as Access Table datatype.. Date/Time does absolutely jack for tracking timestamps formatting a field control or input mask or display format of the table column doesn't do anything for this. Hire some real app developers from the SQL team to create a application that is better for developers.. not office secretary. Take your head out of your ass, this application needs a smarter Project Manager, who actually knows developers hate Access 2007 with a passion, and don't think MS listens to www.MakeOfficeBetter.com

All the examples on the Access Blog, are from people who don't know UI design and build garbage databases.. I've only been developing databases in Access for 3 years, and would like a really IDE for creating databases that is powerful, not stupid.

Having tables is not a database, its just an overglorified excel spreadsheet.. come on, developers need some real respect from MS.

UX designers need to know, UX makes all the difference.. and clearly having 5 versions of Access exactly the same with a new version number is not progress.. then making the next one with less user space, crappy UI ribbons and over zealously database window pane is not progress.. and nobody worries about having the ability to upload access database data to Sharepoint.. that is why its in the F'in database so we can do data analysis, charts, graphs, reports for managers (not the kind at microsoft, but those who care about quality, numbers and productivity, tracking info from materials, production systems, employee performance, employee records, anything and everything.. not some stupid.. spreadsheet as a database.

Have I said it, you really need to get rid of the Project Managers for Access and Just look down the hall the SQL Server and Visual Studio teams.. to create a better Version of Access.

If Access was just used for personal at home use, which is not even included in the SOHO version of OFFICE, people at home don't do mini databases, they use Excel, businesses use Access all the time and not sharepoint for anything out side of storing a copy of query data on a portal site. And no, they are not collaborating on multiple people updating that sharepoint xls file. Depite what you think people are doing with Access and Sharepoint, we dont develop databases to do that.. its not needed, since Access databases can be accessed on a network drive and locked down with Active directory permissions.. they VPN in to use the database, which Access Multiuser record locking is F'ing broken too.. and has been in Access 97..

Clearly the Access team is very dumb.. fire them all, please for the love of God, make a better access version for developers, PLEASE!!!!

BeoStyx

Holy *.

My big question is why did you guys not just come out and say "We have made a quatum leap with the direction we are taking Access..." and why not add that you are introducing some radical new concepts in writing code (especially converting that code to JavaScript for you)? Don't get me wrong, I'm ready to embrace this brave new....world. But putting a "Oh we just added this, and we're doing this now, and you're going to like this but don't mind the shellshock..." face on it all is a bit disconcerting.

I expect a plethora of post release documentation to help us through these changes. I do NOT expect to go out and buy a whole new set of books to have them explained to me.

Otherwise, I like what I see. I was just in a downright quandry on contemplating how to move my Access app to the web: total rewrite using Expression Web? Silverlight? How much more time would I have to invest. Then you all handed this little treasure. Actually it's a godsend. For now I say screw the costs: let me do my experimenting with the betas, and I'll let you know how we're looking on a bank loan.

I see understandable gripes in this thread. But once you all understand the little fact (sarcastically) that this is a paradigm shift, you might like what's going on. I just wish the developent guys would have made that point a little bit clearer.

WoodyS

I agree with Brice in some areas and disagree in others.

It is important for the customer to use the right tool for the right problem. Having programmed in .Net for almost four years I realize that it is a better solution for corporate or enterprise applications, especially where a web app is concerned. But Access is actually a better tool for small business; I mean busineses in the one to five million a year category.

I like the Ribbon Interface and promoting 2003 is to no avail. The industry is not going to go backwards. Reduce and Simplify is the clarion call of small businesses, and Access fits that montra to a "T". Using the larger tools for problems involving less that a quarter million records is like rolling out an Air Bus when a 737 will do.

I just wish Microsoft would market it (Access 2010) for more small business solutions. Nobody uses it for receipies and socker games. Many small businesses need to be using it instead of spreadsheets. In the hands of a professional developer it can do wonders for a small to medium size business.