G
Guest
Hello,
I have built a database to collect data for a clinical trial.
I need to deploy this database up to 8 different users which will work on
very different environments. Some has Access 2003, few has Access 2000 and
some…nothing.
My idea is to use Access 2003 Developers Extensions along with Access
Runtime and I hope that by hitting the button it will make a package that
will run on any environments without having to deal with different solutions
for each user. Will see what happen…
My questions are:
1) since I need to secure my database, I’m thinking of building the .mdw
file through code the very first time the application run (and folks, this is
going to be a challenge…). I cannot build and delivery it to users because
each of them will have different string for target. Is this right?
2) I should then manage the scenario of using my .mdw and not the system.mdw
file.
Since I don’t know if there’s a way to create a shortcut through code (if
there is, I beg you for any hints you can share with me) and I don’t want to
ask user to join the My.mdw for all their Access session, I’m thinking of
building kind of a procedure that will open the db… set the
‘SetDefaultWorkgroupfile’ property pointing to my.mdw… close the db…reopen it
and when close the db by hitting a command button on the main form restores
the ‘SetDefaultWorkgroupfile’ to the system.mdw. Ideally it should work…
practically I’m sure I’m going to face oceans of error messages. But I’m an
optimistic person… at least at this hour of the day…I will let you know how I
feel in the afternoon after lines and lines of code and after tons of
‘slammed out’ from my db due to my security-setting.
So… that’s it. Any help/suggestion is greatly appreciated, especially before
I start this kind of “mission impossible†and learn after a while that all
this is going to be definitely wrong. And be kind… all this sounds desperate
because it IS desperate: the deadline was two days ago.
Rocco
I have built a database to collect data for a clinical trial.
I need to deploy this database up to 8 different users which will work on
very different environments. Some has Access 2003, few has Access 2000 and
some…nothing.
My idea is to use Access 2003 Developers Extensions along with Access
Runtime and I hope that by hitting the button it will make a package that
will run on any environments without having to deal with different solutions
for each user. Will see what happen…
My questions are:
1) since I need to secure my database, I’m thinking of building the .mdw
file through code the very first time the application run (and folks, this is
going to be a challenge…). I cannot build and delivery it to users because
each of them will have different string for target. Is this right?
2) I should then manage the scenario of using my .mdw and not the system.mdw
file.
Since I don’t know if there’s a way to create a shortcut through code (if
there is, I beg you for any hints you can share with me) and I don’t want to
ask user to join the My.mdw for all their Access session, I’m thinking of
building kind of a procedure that will open the db… set the
‘SetDefaultWorkgroupfile’ property pointing to my.mdw… close the db…reopen it
and when close the db by hitting a command button on the main form restores
the ‘SetDefaultWorkgroupfile’ to the system.mdw. Ideally it should work…
practically I’m sure I’m going to face oceans of error messages. But I’m an
optimistic person… at least at this hour of the day…I will let you know how I
feel in the afternoon after lines and lines of code and after tons of
‘slammed out’ from my db due to my security-setting.
So… that’s it. Any help/suggestion is greatly appreciated, especially before
I start this kind of “mission impossible†and learn after a while that all
this is going to be definitely wrong. And be kind… all this sounds desperate
because it IS desperate: the deadline was two days ago.
Rocco