Question Code works in accdb but not in accde

[mcdhappy80]

I don't wish to get into the details here, I just wanna know is there a known issue already why piece of code that works in accdb does not work in accde mode?
Thank You

 

[DCrake]

Very little to go on here perhaps more info could lead to a more intuative answer.

 

[mcdhappy80]

Well, a more general info would be that I had a piece of code which unpacked the zip archives using installed winzip version.
I tried to remove the necessity of having winzip installed so i found a piece of code that extracts the archive but with native windows winzip extraction method, and this works fine in accdb version of database but in accde it generates errors.

 

[Galaxiom]

Does the failure still happen if the accdb file is forced to run in runtime mode using the /runtime commandline switch?

 

[mcdhappy80]

Does the failure still happen if the accdb file is forced to run in runtime mode using the /runtime commandline switch?

I haven't tried that because I distribute accde versions of database not accdb.

 

[gemma-the-husky]

i would think that one reason might be references

in an mdb some reference issues can be sorted automatically by access
in an mde they cant get sorted, and throw an error

just a thought. I think that's maybe one reason why galaxiom asked about the run-time text.

 

[boblarson]

Give the runtime switch a test like G said so you can track down the problem. Remember, troubleshooting means taking advantage of every trick you have available so that you can eliminate certain things up front and then concentrate on others.

It may seem insignificant to use the runtime switch on an accdb to test but it can be very helpful since if it can reproduce the error, you can actually debug the accdb set as accdr or using the /runtime switch where you can't debug code in an accde.

 

[boblarson]

And the answer is YES, there can be code which won't run in an ACCDE but will in an ACCDB.

 

[mcdhappy80]

Thank You for Your answers, I'll refer back as soon as I try this.

 

[theKruser]

I have run into similar instances in the past. In more than one of these instances, it was due to not compiling the code before the accdb->accde conversion. Just thought I would throw that out there.

 

[rick roberts]

could someone explain to me what the runtime command switch is and where to find it?
thanks

 

[boblarson]

could someone explain to me what the runtime command switch is and where to find it?
thanks

If you are using Access 2007 or above just rename the file accdr from accdb or accde.

If you are using Access 2003 or previous, you have to open it up using a shortcut or in the command line window like:

C:\YourPathAndFileName.mdb /runtime

 

[rick roberts]

how does this differ from the packaged version?

 

[gemma-the-husky]

it doesn't. all versions of access are exactly the same for a given release. the runtime version is the full version with certain regisrty settings set that make it work in a reduced functionality mode, and which is given away FOC.

that is why changing the database name works - it just makes access work in a slightly different way.

 

[rick roberts]

so there is no way of knowing explicitly what the error is if it only occurs at runtime and doesnt give an error number how are we to know how to rectify it?

 

[vbaInet]

so there is no way of knowing explicitly what the error is if it only occurs at runtime and doesnt give an error number how are we to know how to rectify it?

It still boils down to error handling as I mentioned in your thread -->

http://www.access-programmers.co.uk/forums/showthread.php?t=216393

You can't run away from it. This is mandatory when creating runtime versions of Access dbs.

 

[gemma-the-husky]

it ought to give an error number. How do you handle errors?

 

[rick roberts]

the error message just says that it has encountered a runtime error and will shut down - thats what i mean about not being able to know why the error occurs and because its runtime it doesnt debug to the code