MAS200 ODBC problems with Access and Crystal Reports...URGENT!!!

I have a large client that just recently upgraded all workstations to Windows XP. Running MAS 200 3.70.  We have several Crystal Reports and Access databases that interface to MAS 200.  The problem we're having is that both interface to MAS 200 very slowly.  I mean it crawls.  We installed the ProvideX driver version 3.31 and it sped up Crystal Reports but made Access a dog. We uninstall it and Access runs fine but Crystal is slow again.  Anyone have problems with the ODBC.  
trifestAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

svenkarlsenCommented:
How do you interface to the MAS200, - standard Access Queries or pass-through queries ?

By using standard querying you will pull all records (like a string of perls) through Access, and have Access do the standard job.

0
svenkarlsenCommented:
How do you interface to the MAS200, - standard Access Queries or pass-through queries ?

By using standard querying you will pull all records (like a string of perls) through Access, and have Access do the standard job.

0
trifestAuthor Commented:
Standard access queries.  
0
svenkarlsenCommented:
Then I suggest you consider using pass-through queries.

Some notes on SQL pass-through queries (SPT's):

 - you cannot use Access module functions in calls
   (i.e.: an SPT should be plain SQL as the server will understand it)

 - Access will not validate your query, - that will be done by the  server

 - You cannot use SPTs as source for subforms

** those were just my worst encounters,  - of course other differences exist, but you must consider
     this something new that must simply be learned ;-)

To make a test to see if SPT will have any effect on your querying, the easiest approach is:

1. Open an Access Db and make some simple selection query for the server in the way you are used to
  - remember: only valid SQL-code! something like: SELECT * FROM [table] WHERE ([something]='whatever');

2. Run the query and time it

3. Open the query in design mode

4. From the menu choose: Query > SQL-Specific > Passthrough

5. Close the query again and test for speed


..... how did it go ?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jadedataMS Access Systems CreatorCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave the following recommendation for this question in the Cleanup topic area:

Accept: svenkarlsen {http:#9673444}

Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!

jadedata
EE Cleanup Volunteer
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.