Advertisement

10.08.2007 at 07:32AM PDT, ID: 22878879
[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!

7.8

Design advice:  Move data Access FE/SQL BE <---> Excel FE/Access BE

Asked by jimhorn in Access Architecture/Design, MS SQL Server, Microsoft Excel Spreadsheet Software

Tags: , , , ,

Our company's enterprise app:
Access front-end (.mdb)
SQL2K back-end, highly normalized

A third-party app I need to move data back and forth:
Excel 2000 front-end (.xls)
Access back-end (.mdb w/zero relationships between tables)

Up until now I was able to write Excel VBA code that executes SP's that move data back and forth, but our third-party vendor just announced that they are going to deny us the password into the Excel front-end, unless we cut them a check, so that will no longer be an option.

Question:  How best to design the transfer of data between these two apps that can be executed from Access FE/SQL BE?

Possible answers, at least currently in my head:
(1)  Create SQL SP's that handle all the INSERT queries, with a parameter for the primary key.
     Then bundle in a DTS package(s) that connects to(from) the Excel2K spreadsheet.
     My current knowledge of DTS packages is limited to simple imports from various data sources into SQL.

(2)  Link tables from the third-party .mdb into our company's enterprise app .mdb, then handle it all via Access VBA and saved queries.

Points awarded for any helpful comments.

TIA
JimStart Free Trial
[+][-]10.08.2007 at 07:36AM PDT, ID: 20034305

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.

 
[+][-]10.08.2007 at 08:43AM PDT, ID: 20034811

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.

 
[+][-]10.08.2007 at 08:47AM PDT, ID: 20034836

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.

 
[+][-]10.09.2007 at 02:11AM PDT, ID: 20039416

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: Access Architecture/Design, MS SQL Server, Microsoft Excel Spreadsheet Software
Tags: access, sql, excel, data, fe
Sign Up Now!
Solution Provided By: Racimo
Participating Experts: 3
Solution Grade: A
 
 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_1_20070628