Selasa, 03 April 2012

[AccessDevelopers] Re: Access front end/SQL Express back end?

 

Okay, thanks again Duane.
Shel

--- In AccessDevelopers@yahoogroups.com, Duane Hookom <duanehookom@...> wrote:
>
> Your solution could work. I do a lot of reporting out of SQL primarily with web and Excel. I use Access as a utility for transforming the data.
>
> Btw, you should probably try to avoid duplicate posting to multiple groups.
>
> Duane Hookom
> MS Access MVP
>
> To: AccessDevelopers@yahoogroups.com
> From: sarmbraugh@...
> Date: Mon, 2 Apr 2012 22:51:45 +0000
> Subject: [AccessDevelopers] Re: Access front end/SQL Express back end?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thank you, Duane. That is all incredibly helpful.
>
>
>
> If you or anyone else has time, I just wanted to throw out some things I'm thinking to see if they make sense to people with more experience...
>
>
>
> So my client gets data in different formats from a bunch of companies, does stuff it, and then packages up some analyses that they send back to the companies. Right now they're using lots of Excel spreadsheets with macros to do this.
>
>
>
> All this data combined seems like it will be too much for Jet. Right now the client doesn't look at data across companies though. They just look at a single company in isolation. Data at the company level seems like it could be handled by Jet.
>
>
>
> The client is also working in an environment where their reporting needs are constantly changing. They want their analysts to have a flexible system that allows them to modify reports and create their own queries, without having to learn a lot of SQL or deal with anything too far afield from what they've been doing with Excel.
>
>
>
> I'm thinking of making something where each user has an Access front end that links to both a SQL Express back end and to the user's own little Access back end. SQL Express will be like a central data repository, and the Access databases will be like a work space. The Access tables will always contain data for a single company only -- so users can import new data into the Access tables, do stuff to it, and then the cleaned data gets sent to the SQL Express "repository" tables. Basic reports can also be run by pulling data for a single company from the SQL Express tables into Access.
>
>
>
> If anyone has feedback on any of that, that would be great.
>
>
>
> Thanks again,
>
> Shel
>
>
>
> --- In AccessDevelopers@yahoogroups.com, Duane Hookom <duanehookom@> wrote:
>
> >
>
> >
>
> > Shel,
>
> > There aren't too many differences between SQL Express and other SQL Server versions. I generally recommend linking to the tables. You can then create queries as if the tables were Access tables.
>
> >
>
> > There are a number of ways to optimize your application with SQL Server tables. Pass-through queries are much better where the data can be read-only.
>
> >
>
> > I use DSN-less connections with code from Doug Steele's page http://www.accessmvp.com/DJSteele/DSNLessLinks.html.
>
> >
>
> > Duane Hookom
>
> > MS Access MVP
>
> >
>
> > From: sarmbraugh@
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Hello,
>
> >
>
> >
>
> >
>
> > I am wondering if anyone has experience with building something with an Access front end + SQL Server Express back end?
>
> >
>
> >
>
> >
>
> > I used to do a lot of development work with Access, but don't have much experience working outside of an Access/Jet environment.
>
> >
>
> >
>
> >
>
> > Some things I'm wondering about are if the Access query builder can be used with SQL Express tables, what's involved in deploying Access with SQL Server Express, and just general things to watch out for.
>
> >
>
> >
>
> >
>
> > Any suggestions or pointers would be greatly appreciated.
>
> >
>
> >
>
> >
>
> > Thank you,
>
> >
>
> > Shel
>
> >
>

__._,_.___
Recent Activity:

Please zip all files prior to uploading to Files section.
.

__,_._,___

Tidak ada komentar:

Posting Komentar