What I've done may not be the easiest way but it works fine:
I wrote an application that create the database and fill it, It has the same
program ID than the main application.
I call it from the main application to build the db and then delete it from
the main application.
let's call our main application "App1" and the db builder "App2"
App2 is hidden (option of the GCC compiler, I don't know for the others)
-App1 detect App2
=>App1 launch App2
-App2 create the DB and an other temporary DB called App2_OK
-App2 launch App1
-App1 detect App2_OK
=>App1 delete App2 and App2_OK
-the program really begin
There are two advantages:
-When you beam or delete you application the DB comes with it
-If you need to update the data, you only have to reinstall App2 and
App1 will do the job for you
That's all
Pierre Baux
Scott Johnson <[EMAIL PROTECTED]> a écrit dans le message :
[EMAIL PROTECTED]
>
> I am developing an application that relies on a database to run. I would
> also like people to be able to beam the application and have the database
> beam with it. I assumed that when you beamed an application using the
Beam
> menu option from the application launcher, that all of that apps databases
> would go with it, but apparently that doesn't happen. Is there a way to
> beam the database without having to program the application to do it
> explicitly?
>
> Thanks,
> --Scott
>
>
>
>
>
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
