I am developing a system which will be delivered as a run-time product where the early months of live operation are likely to see the need to revise and add to the repertoire of text generation functions. Wherever possible I've tried to use table data ( queries ) but there are many cases where program code is required. (If Access had stored procedures then this would probably solve my problem.)

My plan was to move all these functions into a library db just containing code modules. I planned to re-issue just the library database if function logic needed to change or additional functions where needed. I realised that problems would arise if any functions used by the the main db were removed but I didn't ( perhaps foolishly !) think there would be any issues if the statements inside a function were amended.

It now appears that any changes made to the library db cause a run-time error. The runtime application certainly uses the library db - if it isn't there then it gives and error. My experiments suggest that any change to the library db will cause an error - it looks as though there is something in the compiled main db which is able to detect if the libary db isn't exactly the same as the db which was used in the compilation/assembly.

Am I right that my original assumption was wrong - you can't change a library db in a run-time application ? And if I am, can anyone suggest a solution to my problem which will allow data manipulation changes to be made without requiring the re-installation of the application ?

Thanks

Peter

We use Inno Setup

If the dll doesn't need installation, I guess it would work. I haven't tried though.

/gustav