Advertisement

03.24.2008 at 01:04PM PDT, ID: 23265142
[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!

8.1

Linking MDB front end to SQL server back end

Asked by DaveIsaacs in Microsoft Access Database, MS SQL Server

Tags: , , ,

I am part of a two-person IT department in a company with approximately 35 computer stations. We have developed a database, beginning 10 years ago in Access 97, upgrading to 2000 and now 2003. Our back end is about 250 MB and the front end 100 MB. We are contemplating moving toward SQL Server but are leary of several problems.
One of our concerns is that we have some key forms that have grown in layers over the years and they are run by rather complicated queries and local tables. These seem to be a no-no for SQL server. To re-write our current front end with our limited staff would take a long time.
We have looked for sources of instruction but everything seems to be directed to a user with more knowledge than we have. Are we traveling down a dead-end?

Start Free Trial
[+][-]03.24.2008 at 01:10PM PDT, ID: 21196460

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 7-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]03.24.2008 at 01:13PM PDT, ID: 21196488

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 7-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]03.24.2008 at 02:03PM PDT, ID: 21196888

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 7-day free trial to view this Assisted Solution or ask the Experts your question.

 
[+][-]03.24.2008 at 02:32PM PDT, ID: 21197153

View this solution now by starting your 7-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

Zones: Microsoft Access Database, MS SQL Server
Tags: Microsoft, Access, 2003, SQL Server 2005
Sign Up Now!
Solution Provided By: LPurvis
Participating Experts: 4
Solution Grade: B
 
 
[+][-]04.04.2008 at 09:30AM PDT, ID: 21283342

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20081112-EE-VQP-42 / EE_QW_2_20070628