Bear with me & I'll tell you a story…My turn to ask for help! There is a question at the end, but I thought it might be useful to give some background information.
I developed an application in Access 97 to be converted into a runtime to distribute. Unfortunately my helpful IT team managed to lose the Office 97 ODE so I couldn't distribute it. They did have the 2000 ODE so I could convert my db and use that to roll out my database.
To make things easier for myself I just used DAO and referenced everything explicitly (using DAO.Database etc.) with a view to changing it when I'm more confident using ADO.
To do the converting a full version of Office 97 was installed on my machine, but not the ODE. (I don't work in IT; therefore I cannot be considered a developer. 3 years of Access, VB & web development count for nothing if your face doesn't fit!)
When the time came to create the runtime & roll out the package to users I thought my job was done! How wrong was I!
Here's the scenario: Users all have Office 97 installed on their machines, but not Access. The runtime is created using 2000 ODE on a different computer over in IT. I am assured it runs fine on his PC, but have not seen it for myself.
When the package is installed on another users machine, everything seems to be fine until you run the file. It opens fine, but as soon as I start to do things in it, it all falls to pieces.
When I try & view a chart I get an error with unrecognised function …. And part of the SQL statement the chart is based one which uses IIF statements.
When I try to import a text file (using my own import routine that reads a line at a time) I get a blank msgbox appearing.
All this happens when running the mde file on the runtime package. When I run the mdb file, I don't even get the package started! The autoexec macro, which refreshes the linked tables and opens the 1st form, just falls over with a runtime error and chucks me out.
I have imported the code from Dev & Terry's reference wizard & set it so it runs when the database opens. According to that there are NO referenced files in the runtime version of the file. In mine there are 7!
I kind of assumed that the P&DW took care of all this references stuff. Is there a problem with the wizard or the person using it? If I need to make my own references, how do I set references from code if the code doesn't run in the 1st place?
Please help me with this; it's coming up to pay review time!
Many thanks in advance
Ben
----------------------------------
Ben O'Hara
Home: bpo@RobotParade.co.uk
Work: bo104@westyorkshire.pnn.police.uk
Web: ----------------------------------
I developed an application in Access 97 to be converted into a runtime to distribute. Unfortunately my helpful IT team managed to lose the Office 97 ODE so I couldn't distribute it. They did have the 2000 ODE so I could convert my db and use that to roll out my database.
To make things easier for myself I just used DAO and referenced everything explicitly (using DAO.Database etc.) with a view to changing it when I'm more confident using ADO.
To do the converting a full version of Office 97 was installed on my machine, but not the ODE. (I don't work in IT; therefore I cannot be considered a developer. 3 years of Access, VB & web development count for nothing if your face doesn't fit!)
When the time came to create the runtime & roll out the package to users I thought my job was done! How wrong was I!
Here's the scenario: Users all have Office 97 installed on their machines, but not Access. The runtime is created using 2000 ODE on a different computer over in IT. I am assured it runs fine on his PC, but have not seen it for myself.
When the package is installed on another users machine, everything seems to be fine until you run the file. It opens fine, but as soon as I start to do things in it, it all falls to pieces.
When I try & view a chart I get an error with unrecognised function …. And part of the SQL statement the chart is based one which uses IIF statements.
When I try to import a text file (using my own import routine that reads a line at a time) I get a blank msgbox appearing.
All this happens when running the mde file on the runtime package. When I run the mdb file, I don't even get the package started! The autoexec macro, which refreshes the linked tables and opens the 1st form, just falls over with a runtime error and chucks me out.
I have imported the code from Dev & Terry's reference wizard & set it so it runs when the database opens. According to that there are NO referenced files in the runtime version of the file. In mine there are 7!
I kind of assumed that the P&DW took care of all this references stuff. Is there a problem with the wizard or the person using it? If I need to make my own references, how do I set references from code if the code doesn't run in the 1st place?
Please help me with this; it's coming up to pay review time!
Many thanks in advance
Ben
----------------------------------
Ben O'Hara
Home: bpo@RobotParade.co.uk
Work: bo104@westyorkshire.pnn.police.uk
Web: ----------------------------------