Error opening application

B

Bart B

We have a database that was used in Access 2003. We upgraded our computer
and software and now we have Access 2007. When trying to run this database
we get the error "Error in opening application: 429 Error creating
CSetupInfo". Any idea what this error could mean? What other info would you
need to know from me?

thanks
Bart
 
B

Bart B

I checked the library references on the old machine and I have the same
libraries on the new machine, but I'm still having the same error.

Any other suggestions?

thanks
 
A

Allen Browne

1. Open the database while holding down the Shift key so that any startup
code does not run.

2. Go to:
Office Button | Access Options | Trust Center | Trust Center Settings
and click the Add button. Add the folder where this database resides to the
trusted locations.

3. Go to:
Office Button | Access Options | Current Database
and uncheck the boxes under Name AutoCorrect

4. Compact the database:
Office Button | Manage | Compact/Repair

5. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

6. Open Access (holding down the Shift key if you have any startup code),
and compact again.

7. Open a code window.
Choose References on the tools menu.
Which libraries are used? (List in your rely.)
Are you certain none of them has the word "MISSING" beside them?

8. Still in the code window, choose Compile on the Debug menu.
Fix any problems, and repeat until it compiles okay.
 
B

Bart B

Well I've tried to take the database to another machine with Access 2003 on
it and I get the same error I was getting on the Access 2007 machine, so I
must have something set different, I just need to find out what. Anybody
have any ideas?
 
A

Allen Browne

Yes it does.

If you create a new database, and import the objects, it may stop at the
point when it reaches the corrupted form.

If not, you can probably identify the corrupted form by exporting your forms
to text files with the undocumented SaveAsText, e.g.:
SaveAsText acForm, "Form1", "C:\MyFolder\Form1.txt"
Loop through CurrentProject.AllForms, and see which one fails.

(If you have code behind your reports, it could be one of them. Or it could
be one of the stand-alone modules, but that is less likely.)
 
B

Bart B

You were right, it was a library file. I searched the registery on the old
machine and found couple .dll files that I needed to register.

But now I have a report that crashes the database when I try to open it.
Any ideas there?

thanks
 
A

Allen Browne

Follow the steps in the 2nd last post to create a new database and import
all the *other* forms/reports except the known bad one.

You can then try SaveAsText to export the bad one to a text field, and
LoadFromText to import it into the new database.

At worst, you have one report to rebuild.
 
B

Bart B

I think have my problem narrowed down to a union query. When I ran a
"Object Dependencies" under "Missing information" it says "union query".
Here is the sql for the union query. Does anything stand out as a problem?

SELECT Graph.ACCT_NO & " 1" AS Seqord, [graph].[M1] AS Expr1, [graph].[M2]
AS Expr2, [graph].[M3] AS Expr3, [graph].[M4] AS Expr4, [graph].[M5] AS
Expr5, [graph].[M6] AS Expr6, [graph].[M7] AS Expr7, [graph].[M8] AS Expr8,
[graph].[M9] AS Expr9,[graph].[M10] AS Expr10, [graph].[M11] AS Expr11,
[graph].[M12] AS Expr12, [graph].[M13] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3)=[Reports]![3series]![MyAccount]
UNION SELECT Graph.ACCT_NO & " 2" AS seqord, [M1_USE] AS Expr1,[M2_USE]
AS Expr2,[M3_USE] AS Expr3,[M4_USE] AS Expr4,[M5_USE] AS Expr5,[M6_USE] AS
Expr6,[M7_USE] AS Expr7,[M8_USE] AS Expr8,[M9_USE] AS Expr9,[M10_USE] AS
Expr10, [M11_USE] AS Expr11,[M12_USE] AS Expr12,[M13_USE] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3)=[Reports]![3series]![MyAccount]
ORDER BY seqord;
 
A

Allen Browne

The attempt to read a value from the report in the WHERE clause looks wrong.

Unlike forms, reports don't have a current record, so a query cannot refer
to the current record in the report like that.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Bart B menard.com> said:
I think have my problem narrowed down to a union query. When I ran a
"Object Dependencies" under "Missing information" it says "union query".
Here is the sql for the union query. Does anything stand out as a problem?
Click to expand...
SELECT Graph.ACCT_NO & " 1" AS Seqord,
[graph].[M1] AS Expr1,
[graph].[M2] AS Expr2,
[graph].[M3] AS Expr3,
[graph].[M4] AS Expr4,
[graph].[M5] AS Expr5,
[graph].[M6] AS Expr6,
[graph].[M7] AS Expr7,
[graph].[M8] AS Expr8,
[graph].[M9] AS Expr9,
[graph].[M10] AS Expr10,
[graph].[M11] AS Expr11,
[graph].[M12] AS Expr12,
[graph].[M13] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3) = [Reports]![3series]![MyAccount]
UNION
SELECT Graph.ACCT_NO & " 2" AS seqord,
[M1_USE] AS Expr1,
[M2_USE] AS Expr2,
[M3_USE] AS Expr3,
[M4_USE] AS Expr4,
[M5_USE] AS Expr5,
[M6_USE] AS Expr6,
[M7_USE] AS Expr7,
[M8_USE] AS Expr8,
[M9_USE] AS Expr9,
[M10_USE] AS Expr10,
[M11_USE] AS Expr11,
[M12_USE] AS Expr12,
[M13_USE] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3)=[Reports]![3series]![MyAccount]
ORDER BY seqord;>
 
B

Bart B

Thanks for being helpful and patient with me.
On a side note, could you tell what the & " 1" means in the SELECT
statement?

Allen Browne said:
The attempt to read a value from the report in the WHERE clause looks
wrong.

Unlike forms, reports don't have a current record, so a query cannot refer
to the current record in the report like that.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Bart B menard.com> said:
I think have my problem narrowed down to a union query. When I ran a
"Object Dependencies" under "Missing information" it says "union query".
Here is the sql for the union query. Does anything stand out as a
problem?
Click to expand...
SELECT Graph.ACCT_NO & " 1" AS Seqord,
[graph].[M1] AS Expr1,
[graph].[M2] AS Expr2,
[graph].[M3] AS Expr3,
[graph].[M4] AS Expr4,
[graph].[M5] AS Expr5,
[graph].[M6] AS Expr6,
[graph].[M7] AS Expr7,
[graph].[M8] AS Expr8,
[graph].[M9] AS Expr9,
[graph].[M10] AS Expr10,
[graph].[M11] AS Expr11,
[graph].[M12] AS Expr12,
[graph].[M13] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3) = [Reports]![3series]![MyAccount]
UNION
SELECT Graph.ACCT_NO & " 2" AS seqord,
[M1_USE] AS Expr1,
[M2_USE] AS Expr2,
[M3_USE] AS Expr3,
[M4_USE] AS Expr4,
[M5_USE] AS Expr5,
[M6_USE] AS Expr6,
[M7_USE] AS Expr7,
[M8_USE] AS Expr8,
[M9_USE] AS Expr9,
[M10_USE] AS Expr10,
[M11_USE] AS Expr11,
[M12_USE] AS Expr12,
[M13_USE] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3)=[Reports]![3series]![MyAccount]
ORDER BY seqord;>
Click to expand...
 
A

Allen Browne

No idea what's going on with that calculated field.
Whoever designed the query wanted a couple of SeqOrds.

It probably won't work with the spaces like that though.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

Bart B menard.com> said:
Thanks for being helpful and patient with me.
On a side note, could you tell what the & " 1" means in the SELECT
statement?

Allen Browne said:
The attempt to read a value from the report in the WHERE clause looks
wrong.

Unlike forms, reports don't have a current record, so a query cannot
refer to the current record in the report like that.

Bart B menard.com> said:
I think have my problem narrowed down to a union query. When I ran a
"Object Dependencies" under "Missing information" it says "union query".
Here is the sql for the union query. Does anything stand out as a
problem?
Click to expand...
SELECT Graph.ACCT_NO & " 1" AS Seqord,
[graph].[M1] AS Expr1,
[graph].[M2] AS Expr2,
[graph].[M3] AS Expr3,
[graph].[M4] AS Expr4,
[graph].[M5] AS Expr5,
[graph].[M6] AS Expr6,
[graph].[M7] AS Expr7,
[graph].[M8] AS Expr8,
[graph].[M9] AS Expr9,
[graph].[M10] AS Expr10,
[graph].[M11] AS Expr11,
[graph].[M12] AS Expr12,
[graph].[M13] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3) = [Reports]![3series]![MyAccount]
UNION
SELECT Graph.ACCT_NO & " 2" AS seqord,
[M1_USE] AS Expr1,
[M2_USE] AS Expr2,
[M3_USE] AS Expr3,
[M4_USE] AS Expr4,
[M5_USE] AS Expr5,
[M6_USE] AS Expr6,
[M7_USE] AS Expr7,
[M8_USE] AS Expr8,
[M9_USE] AS Expr9,
[M10_USE] AS Expr10,
[M11_USE] AS Expr11,
[M12_USE] AS Expr12,
[M13_USE] AS Expr13
FROM Graph
WHERE mid(Graph.ACCT_NO,3)=[Reports]![3series]![MyAccount]
ORDER BY seqord;>
Follow the steps in the 2nd last post to create a new database and
import all the *other* forms/reports except the known bad one.

You can then try SaveAsText to export the bad one to a text field, and
LoadFromText to import it into the new database.

At worst, you have one report to rebuild.

You were right, it was a library file. I searched the registery on the
old machine and found couple .dll files that I needed to register.

But now I have a report that crashes the database when I try to open
it. Any ideas there?

thanks

Yes it does.

If you create a new database, and import the objects, it may stop at
the point when it reaches the corrupted form.

If not, you can probably identify the corrupted form by exporting
your forms to text files with the undocumented SaveAsText, e.g.:
SaveAsText acForm, "Form1", "C:\MyFolder\Form1.txt"
Loop through CurrentProject.AllForms, and see which one fails.

(If you have code behind your reports, it could be one of them. Or it
could be one of the stand-alone modules, but that is less likely.)

does it matter that I still get the error, when trying to decompile


1. Open the database while holding down the Shift key so that any
startup code does not run.

2. Go to:
Office Button | Access Options | Trust Center | Trust Center
Settings
and click the Add button. Add the folder where this database
resides to the trusted locations.

3. Go to:
Office Button | Access Options | Current Database
and uncheck the boxes under Name AutoCorrect

4. Compact the database:
Office Button | Manage | Compact/Repair

5. Close Access. Make a backup copy of the file. Decompile the
database by entering something like this at the command prompt
while Access is not running. It is all one line, and include the
quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe"
/decompile
"c:\MyPath\MyDatabase.mdb"

6. Open Access (holding down the Shift key if you have any startup
code), and compact again.

7. Open a code window.
Choose References on the tools menu.
Which libraries are used? (List in your rely.)
Are you certain none of them has the word "MISSING" beside them?

8. Still in the code window, choose Compile on the Debug menu.
Fix any problems, and repeat until it compiles okay.


--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

I checked the library references on the old machine and I have the
same libraries on the new machine, but I'm still having the same
error.

Any other suggestions?

thanks


In that case, is it probably a problem with library references.

See:
Solving Problems with Library References
at:
http://allenbrowne.com/ser-38.html

No, it's running windowx xp sp2


Bart, is the new computer running Windows Vista?
If so, see:
Errors using multiple versions of Access under Vista
at:
http://allenbrowne.com/bug-17.html

We have a database that was used in Access 2003. We upgraded
our computer and software and now we have Access 2007. When
trying to run this database we get the error "Error in opening
application: 429 Error creating CSetupInfo". Any idea what
this error could mean? What other info would you need to know
from me?
Click to expand...
Click to expand...
Click to expand...
 
Top