Trying to link Access and ODBC tables

[Madawc]

Someone at work is trying to add a table that they've created using Microsoft Access 2002. We use Crystal 8.5, mostly with 'ODBC'. It would be convenient to be able to use both in the same report, rather than putting one or other in a subreport.

When we tried it, Crystal allowed a link, refused to let it be anything other than equal . It also failed to return any data, , so we fixed it with a subreport - it is a very small database.

Is a direct link actually impossible? And does this limitation still apply in higher versions of Crystal?

Madawc Williams (East Anglia, UK)

 

[GJParker]

We use Crystal 8.5, mostly with 'ODBC'
[\quote]

ODBC is a connection type, what database is the ODBC connection connecting to ?

one way round this could be to link the Access table into your main database if this is possible, this should allow the linked table to be available via your ODBC connection.

HTH

Gary Parker
MIS Data Analyst
Manchester, England

 

[Madawc]

Databases aren't my area. Just how would I find the type?

Madawc Williams (East Anglia, UK)

 

[Turkbear]

Hi,
Try using the Set Location option from the Database menu when the report is open in CR..

Then look on your machine to see whare that ODBC DSN is 'pointed'..

Just a question, How can you be expected to design a report that is efficent in accessing data if you are not given such BASIC information as the type and version of the database the data is in????

 

[Madawc]

Thanks for your interest. Our core functions are done using a Unisys mainframe. Crystal is 95% used for a copy of that database, updated daily so that the data stays relevant. It doesn't need to be very efficient, because it's not the core of what we do. The problem I had was for a small database used for internal purposes.

SQL commands are used for creating and handling the database itself. But that's done by another department who have lots of other work.

Madawc Williams (East Anglia, UK)

 

[GJParker]

Try linking the required tables from your mainframe into the Access database, this will then make them avaiable using just the Access connection.

As I'm un familiar with UNISYS mainframes I couldn't say whether this will allow you to do more complex joins within crystal, but it's worth a try. If this doesn't work you could try and create a view in access with the linked tables and see if this gives you more options.

HTH

Gary Parker
MIS Data Analyst
Manchester, England

 

[synapsevampire]

If I understand this correctly, you have an ODBC connection and an Access table to join.

As Gary alluded to, create another Access database and Link (not import) both the Access database and the Unisys
table(s) into the new Access database. Now you can create a single query within Access as the data source with lots of flexibility, and Access is faster than Crystal so the performance will be better.

-k

 

[Madawc]

Thanks. Since the current problem was just for a small database used for internal purposes, there is no real performance issue. If we need something for a bigger database, I'll follow your advice.

Madawc Williams (East Anglia, UK)