Microsoft Access and Progress 10.1A

[Guest]

Hello, I created a microsoft access 2000 application that had a linked table
to a table in a Progress 9.1 database. The data from the linked table was
joined to data in the Access file to create an editable data grid form and a
report. Everything was working fine until the customer upgraded their system
to a Progress 10.1. After that the database would not work at all. We found
out that adding a workaround code to the ODBC data connector
(worarounds2=8192) that Access could then return data from Progress. However,
when I attempt to open the query that joined the data from Progress and the
data existing in the application Microsoft Access runs out of memory and
locks up. I found that if i altered the query not to join the data coming
from Progress this did not happen. Before the upgrade everything seemed to
work fine. Does anyone have any suggestions as to how this could happen and
what I could do to circumvent this problem?
-Robert

 

[dbahooker]

Access MDB is unreliable

use SQL Server and a real ETL tool to copy the info into SQL Server
and then use Access Data Projects


anything else is a waste of resources; because MDB is obsolete; and it
has been for 10 years

 

[Arvin Meyer [MVP]]

You might build an intermediate database that extracts only the data that
you need. I just had to do this with a dBase proprietary format database
that had over 40 GB of data in it. I created a query that extracted the 120
MB of data that I needed to run my reports and used that to populate a table
which I linked to. Every morning, when I open my database, I run code which
deletes the old database, creates a new one from the 40 GB of original data,
then creates an index and links to the table with about a half million rows
of data. The entire process takes under 30 seconds.

 

[dbahooker]

sorry kid

N-tier Access Databases are completely unacceptable

use TEXT files and BULK INSERT, you don't need 9 different MDB files
to do this type of thing

JUST A SINGLE SQL SERVER DATABASE

 

[dbahooker]

yeah, you should 'link to a table with a half dozen rows'

ROFL

you mean it takes 30 seconds every time you OPEN the table before it
starts showing the first dozen records?

LINKED TABLES ARE FOR RETARDS, AND ACCESS MDB MAKES SQL PASSTHRUS TOO
DIFFICULT

move to SQL Server kids

 

[Susie Johnson]

Access doesn't reliably work with such large datasets

I reccomend moving to SQL Server and using a real ETL tool like DTS or SSIS