A2003 application db file not working

[RonMcIntire]

All:

I have a db file running under A2003 that for some reason now does not work. The "Trim" and "Left" functions are not recognized, at least one table is missing and all links to that table are broken. I suspect Office 2003 SP3 is the culprit but cannot prove it. Other db files I use don't seem to be affected. The application contains a sizeable number of queries that use multiple queries to print reports.

A forum thread asked "Have you installed Hotfix?" I've downloaded the file, but the installation readme.txt is way over my head.

Three Questions:

1. Am I correct in assuming SP3 is the problem?

2. Is this something Hotfix can resolve?

3. Would someone please step me through the basics of installing Hotfix?

Thanks. As it stands I am having to re-link many of my queries and at least the one table. Not a pretty task I look forward to.

Ron

 

[PHV]

The "Trim" and "Left" functions are not recognized
Check the References in the VBE.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[MazeWorX]

relinking the tables should resolve any query issues. Did you move the db? Use the Linked table manger to relink all tables. I know of functions within access being disabled when it is opened in sandbox mode. Although I believe this applies to 2007 and up. Simply adding the db as a trusted location resolves the issue.

Use Window Update to install your hotfixes.

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>

 

[RonMcIntire]

MazWorX:

Thanks for your input. I'll use Windows update to install hotfix.

As to my problem: It is now resolved. Without too much detail, I import several external tables then rename them to update my data. I simply renamed the new tables in the wrong sequence and, of course, the query links were broken. I may still create a front and back end for my app but at a later date.

I did have a reference problem but removing one of the references resolved that problem too.

Thanks for you help.

Ron

 

[MazeWorX]

glad to here. A note about split db's the easiest way to corrupt a db is NOT to split it. Split the objects from the data sooner rather than later to avoid this scenario other wise the next post might be 'How do I recover a corrupt db?'

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work" <<Edison>>