Runtime?

[SteveF]

I have a database at a stage where I want to give it to other people for testing etc. What I don't want is for the people who test it to be able to see the structure or be able to make any changes. I'm thinking that the answer is 'Runtime' but I'm not sure.

I'm using Access 2003 and the database is in a 2000 format. My access version was part of a MS Works suite so no developer tools etc. I've looked on the Microsoft site but came away pretty confused.

Any help appreciated.

 

[georgedwilkinson]

I don't have that version installed here but look into making a MDE file (plain jane Access functionality). Make sure you maintain control of the original version. You should do a considerable amount of reading on this before you make final decisions since there are some gotchas.

 

[SteveF]

I do have the option for an MDE file so will give that a try. What are the 'gotchas' ??

 

[georgedwilkinson]

The gotchas are related to the nature of the "compiled" mde file. You cannot make any changes to the structure of an mde file (that means tables, forms, reports, and code can never be changed). You can't reference an mdb file from an mde file. With that in mind, you should consider any other security and splitting the database well in advance and make sure you have a process in place to provide updates. In essence, you need to test using mde just like you'd test any other major system change.

 

[boblarson]

The gotchas are related to the nature of the "compiled" mde file. You cannot make any changes to the structure of an mde file (that means tables, forms, reports, and code can never be changed).

Slightly incorrect George. The use of an MDE (or MDB) with the Runtime means no design changes whatsoever. However, if you have a full version of Access you can still make changes to tables and queries in an MDE file. Yep, believe it or not you can.

You can't reference an mdb file from an mde file.

What do you mean by that? You can link to an mdb file from an mde file.

The main "gotchas" around the use of an mde file with the runtime is that you need to ensure that you have bullet-proof error handling and you need to provide any toolbars that your users will need as the runtime will not give your users any toolbars you don't provide.

As for the MDE file, it will compile all code and macros so that users cannot view it and it will not allow any design changes to forms and reports. But as mentioned before, with a full version of Access, you can still modify an MDE's table structure and queries.

 

[SteveF]

Thanks for that, an MDE file sounds like a good solution for me just now.

Edit: Just read the last post, I will need to be careful testing methinks. It's not earth shattering stuff I'm doing, it's just been a lot of work and I want to be careful where it goes etc.

 

[georgedwilkinson]

Slightly incorrect George. The use of an MDE (or MDB) with the Runtime means no design changes whatsoever. However, if you have a full version of Access you can still make changes to tables and queries in an MDE file. Yep, believe it or not you can.

Agreed. That is something that SteveF needs to consider when testing whether an MDE is right for his situation.

What do you mean by that? You can link to an mdb file from an mde file.

Just reporting what I've read. I take it to mean that you cannot run a sub/function in a module of an mdb file from an mde file.

Also, it is unclear to me whether the OP is considering the use of the runtime or has definitely settled on it's use. Hard to answer the question precisely so I've tried to be as generic (and pessimistic) as possible. The fact is, anybody who is considering security needs to do all the research to find what will work for their situation. I'd hate to say "yeah, mde files are the greatest thing since sliced bread", have my suggestion being taken, and then the poor guy finds he's lost the ability to manage versions, or worse.

 

[SteveF]

Also, it is unclear to me whether the OP is considering the use of the runtime or has definitely settled on it's use. Hard to answer the question precisely so I've tried to be as generic (and pessimistic) as possible. The fact is, anybody who is considering security needs to do all the research to find what will work for their situation. I'd hate to say "yeah, mde files are the greatest thing since sliced bread", have my suggestion being taken, and then the poor guy finds he's lost the ability to manage versions, or worse.

It's as much a question about Runtime as anything else. I'm still very new to Access and databases, so much of what is posted goes right over my head, but I try and take things in and then go away to test it; more often than not coming back with more questions until I get where I want to be.

The reality is that I've put a whole load of work into a database and it is doing (almost) everything I want it to do. What I want now is to give it to someone else and get some feedback, but I don't want to give all my work away and am exploring my options.

I've not settled on Runtime or any other solution, I'm just trying to understand the 'what ifs' so all thoughts are appreciated.