Importing Queries and Reports into a new database

[access dummie]

Each month, I download text files from our business mainframe system. The
text files are imported into Excel and then imported into Access as different
tables. I then import queries and reports from the previous month's Access
database. So I am creating a new database each month to manipulate current
month's data into reports that I regularly need.

I am using the 2007 version, but the queries and reports were created in
earlier versions.

Each time I go through this process, nearly every field in my queries is
"renamed" [Expr1]:Acct#, etc. thus causing a parameter prompt when trying to
execute a report.

I have made the changes to the queries and re-imported, but the "Expr" still
comes back.

At first, I was using 2007 and saving as a 2000-2003 format. In hopes of
correcting the problem, I began saving it in the 2007 format...same problem.
I read about the trust center issues, so I included the folders where the
previous month's database is located. That didn't work.

Please help!

 

[Klatuu]

Why do you find it necessary to
1. Import first in to Excel then into Access?
2. Create a new mdb each month?

This could all be done in one Access database without using Excel at all.

Can you describe the process in a bit more detail, especially the format of
the text file, please?

 

[access dummie]

Let me start with--this was the procedure in place when I came to work here.

I work at a financial institution. We download certain account information
from our mainframe (not onsite, but I'm guessing it is of the AS400 type of
system) each month. When downloaded they are in a text format. Our
mainframe is actually writing the information into a report, so we "clean up"
the info in Excel before importing it to Access. We manipulate the data into
certain reports that our mainframe's software doesn't provide.

The database is very simple in that it is just a one day snapshot of our
customer base. Building a complex database to compile each month's data into
one mdb is not necessary for our purposes.

The import from Excel into Access isn't my problem. The problem is when I
import queries and reports from the previous month's mdb. This procedure
worked seamlessly when using a previous version of Access (whatever version
my boss uses).

Why do you find it necessary to
1. Import first in to Excel then into Access?
2. Create a new mdb each month?

This could all be done in one Access database without using Excel at all.

Can you describe the process in a bit more detail, especially the format of
the text file, please?

Each month, I download text files from our business mainframe system. The
text files are imported into Excel and then imported into Access as
different
tables. I then import queries and reports from the previous month's
Access
database. So I am creating a new database each month to manipulate
current
month's data into reports that I regularly need.

I am using the 2007 version, but the queries and reports were created in
earlier versions.

Each time I go through this process, nearly every field in my queries is
"renamed" [Expr1]:Acct#, etc. thus causing a parameter prompt when trying
to
execute a report.

I have made the changes to the queries and re-imported, but the "Expr"
still
comes back.

At first, I was using 2007 and saving as a 2000-2003 format. In hopes of
correcting the problem, I began saving it in the 2007 format...same
problem.
I read about the trust center issues, so I included the folders where the
previous month's database is located. That didn't work.

Please help!

 

[Hunter57 via AccessMonster.com]

Hi,

Usually you get the [Expr1]: in a query when the table or field does not
exist in your database, but did in the database in which the Query was
created. Check to see if you have all the tables and fields the query uses
in your database.

Patrick Wood
http://gainingaccess.net
Free Tutorial series on building a Date Dialog Form for Forms and Reports,
and using Outlook from Access.

Let me start with--this was the procedure in place when I came to work here.

I work at a financial institution. We download certain account information
from our mainframe (not onsite, but I'm guessing it is of the AS400 type of
system) each month. When downloaded they are in a text format. Our
mainframe is actually writing the information into a report, so we "clean up"
the info in Excel before importing it to Access. We manipulate the data into
certain reports that our mainframe's software doesn't provide.

The database is very simple in that it is just a one day snapshot of our
customer base. Building a complex database to compile each month's data into
one mdb is not necessary for our purposes.

The import from Excel into Access isn't my problem. The problem is when I
import queries and reports from the previous month's mdb. This procedure
worked seamlessly when using a previous version of Access (whatever version
my boss uses).

Why do you find it necessary to
1. Import first in to Excel then into Access?

[quoted text clipped - 33 lines]

 

[Klatuu]

There are some differences in 2007. Those thing written in previous
versions, in most cases, should work.

I would suggest you import a copy from the older version, get it working
correctly in your 2007 version and continue to use that version rather than
import from the old version.

Let me start with--this was the procedure in place when I came to work
here.

I work at a financial institution. We download certain account
information
from our mainframe (not onsite, but I'm guessing it is of the AS400 type
of
system) each month. When downloaded they are in a text format. Our
mainframe is actually writing the information into a report, so we "clean
up"
the info in Excel before importing it to Access. We manipulate the data
into
certain reports that our mainframe's software doesn't provide.

The database is very simple in that it is just a one day snapshot of our
customer base. Building a complex database to compile each month's data
into
one mdb is not necessary for our purposes.

The import from Excel into Access isn't my problem. The problem is when I
import queries and reports from the previous month's mdb. This procedure
worked seamlessly when using a previous version of Access (whatever
version
my boss uses).

Why do you find it necessary to
1. Import first in to Excel then into Access?
2. Create a new mdb each month?

This could all be done in one Access database without using Excel at all.

Can you describe the process in a bit more detail, especially the format
of
the text file, please?

Each month, I download text files from our business mainframe system.
The
text files are imported into Excel and then imported into Access as
different
tables. I then import queries and reports from the previous month's
Access
database. So I am creating a new database each month to manipulate
current
month's data into reports that I regularly need.

I am using the 2007 version, but the queries and reports were created
in
earlier versions.

Each time I go through this process, nearly every field in my queries
is
"renamed" [Expr1]:Acct#, etc. thus causing a parameter prompt when
trying
to
execute a report.

I have made the changes to the queries and re-imported, but the "Expr"
still
comes back.

At first, I was using 2007 and saving as a 2000-2003 format. In hopes
of
correcting the problem, I began saving it in the 2007 format...same
problem.
I read about the trust center issues, so I included the folders where
the
previous month's database is located. That didn't work.

Please help!