Advertisement

01.31.2007 at 06:52AM PST, ID: 22143652
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.8

migrating TABLES ONLY from access to sql server (but keeping an access front end). best practice tips

Asked by PatrickK_W in Microsoft Access Database

Hi.

Just a quick(ish) question.

A client wants me to migrate an old and access database to sql server and also rework and renormalize the tables (we didn’t write the database, it’s a legacy system). The database is heavily used daily by about 10-15 people. They want to keep the front end in aceess (ie link the tables into the access forms in the “front end”).

i was wondering if there is actually any benefit to keeping the front end in access rather than write a .net 2 client for it (either vb or asp.net)?

The main problem at the moment is the number of users and the scalability of access. If I migrate the data to SQL Server this will help a bit, but if I want to use stored procedures, etc (which I do) then i’ll have to re-write every access form anyway and manually access the stored procedures via ADO. Wont I? if this is the case I’ll be able to write a shiny new .net client in about the same time it’ll take me to get sued to working with ado, recordsets and access forms again!

Is there any other way of using SQL stored procedures in access? I have to be honest I haven’t done this in a long time and hardly ever use Access these days.

Why access knowledge is probably outdated now (I haven’t really used it sicne access xp) so there might be better interfaces, etc. they will be using access 2003 by the way.


Thanks for any tips
Start Free Trial
[+][-]01.31.2007 at 07:58AM PST, ID: 18436781

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: Microsoft Access Database
Sign Up Now!
Solution Provided By: Data-Man
Participating Experts: 1
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-44