Tech Talk: Using Access with SQL Server Panel Discussion from TechEd 2008

Here in a littel island is Spain, it's cool hear and see MARY, LUKE, ARVIN, POUL ... but, ... nothing new in the conference... , oh yes, someting new! , ... is Ken Getz with an Apple Laptop? ... probably reading mails??? ...

In my experience SQL server is complicated and expensive. I migrated some of my projects to MySql 5.0 retaining the same ms access front end with just a very little debugging and fine tuning in the backend.

After listening to the whole presentation it still seems to me that as long as you're not trying to put a large multiuser security sensitive app onto the web, Access is still highly relevant & useful....and that many IT departments still hate it.....

Clint. . .

When are you going to respond to any of my inquiries? Why you never answer?

Edwin,

I don't have the bandwidth to respond to every email that I get from customers. My primary responsibility is working on the next version. We have other people in our support organization that are responsible for working through customer issues. Most of the time I try to point people in the right direction where they can get the answer. I just searched my inbox and deleted items folder and didn't see anything from you. It might have got deleted in the junk mail folder? Not sure--If you resend me your inquiry I can try and get back to you.

sql server should be made more friendly back end for access. access should be designed as front end for sql server just as for jet engine or ADE. Access front and sql server back end is best combination for easy solution in my opinion.

Don't you think video would make the instructions easier to follow?

Hi Clint, We are hoping the next version Access 14 is not a repacked Access 12. The entire MS Access Developers are expecting this 2 most important Enhancements: 1. Enable as to compile MDE+Runtime into a single EXE, like RBASE, Foxpro.

2. Enhancement of MS ACCESS ADP >>sql server should be made more friendly back end >>for access. access should be designed as front end >>for sql server just as for jet engine or ADE. Access >>front and sql server back end is best combination >>for easy solution in my opinion. ADP is a great Technology; to enable us connect to other DB Server Backend. Not SQL Server Exclusive! Anyway, if the no. 1 enhancement is impossible, we have other expensive alternative www.thinstall.com. And again if the no. 2 enhancement is impossible, we have free alternative MySQL or Postgre. Pls answer us actively.. thanks.

Clint, thanks for your answer. . . I have never send email to you excep when you told us to, you told us to send you email in a post where you named, tell me how are you using the ribbon, you posted an email account, and i send you screen shots and others. However. . . I have asked you many time different questions here. . . in the blogs you have created. I have done this many time, and never have received answer :-) I cannot recall all of them, but i do recall one that sumarizes all. . . Here is the link for the blog: blogs.msdn.com/.../access-source-code-control-and-team-foundation-server.aspx the blog was called : Access Source Code Control and Team Foundation Server I have been reading emails and blogs and have seen a lot of good comments, i think those should be taken seriously, is the access developer comunity that uses access everyday. Like i have said before, i know you should be very busy, abd your bandwidth is not very flexible, but i just hope to get some answers, and that you hear my ideas. Sorry if i was too rude, it was not my intentions. By the way, inever expect access apps to be compiled as an executable, thats why we have the runtime. Clint, keep on doing your good work, we all love you my friend . . .

Edwin--I will try to be more responsive to questions in the blog. In your previous post you asked lots of questions about the future of the product. I'm not at liberty to talk about Office 14. We want to be intentional about how disclosure works and make sure we talk about things that we are pretty certian about. If we talk to early we risk setting expectations that might change. Trust me--we have heard (and take them seriously) many of the issues you raised in that post. I just can't comment on what is in and what is out.

I fully understand your position, ans that was really the purpose of my post, that you see where at we headed, and what are really our concerns as the people who really use access in the real world. You know what, listen to this. Like 2 years ago, before access 2007 came to the market, i was really in a decision, on weather to change one of my apps to vb2005, at that time, or leave it in access, we were havving problems with some features, that were really specific to access. I talked to some guys from microsoft, and in las vegas i contacted a guy from your team ;-) he did not talked about specific features, but he said something like: DAO is your friend. . . That really keep my in the right direction, then i kept access as my patform, im glad i did it that way. As the people who really use access everyday, for many clients, we need to know where are you guys headed, we do not need to know specifics. But things like "conditional formatting is being revised", will keep many guys from choosing third parties or even go away from access because of the use os a grid. One thing that is being commented since access 97, is the support to continuos forms, as a grid And of course more integration with sql server in liked tables. Look at this, access forms now resize that is a great feature, but is only one control in the form that can be the fill, well, maybe all you need now is a table lay out panel, like visual studio, and that will make really usable control for access, so every control can gro in its own boudaries. . . My friend, again thanks for your response, i hope to hear soon from you. Edwin