package solution - am i doing this correctly?

[humph]

I am trying to package and distribute an Access Database which is 2007 format but I am using Access 2010. The package does not have an autoexec macro but the display form is set.

I have unsuccessfully spent the weekend trawling the web and this site to try to find the correct steps.

The machine I am working on is 64 bit and the Access package is 32 bit which appears to be ok. The steps I am proposing are below:

1 debug the the database
2 split the database ( at the moment I havent loaded anything to automatically connect Be / front end but was going to look at this when I get this working )

3 Question 1 do I convert front end to an ACCEDE front end - I don't want users near the code. Or do I leave it to the package solution to create and ACCDR file

4 Question 2 users may or may not have full copies of access and I would like to adopt the middle option " REquire the microsoft to be downloaded if Access not already installed" As I mentioned I don't want users near the code - there is extensive VBA and very few actual macros - is this the best way to protect the code without going overboard on security.

5 "Question 3" Root Directory I have read various comments that we should not add to the program files directory within users machines - What advice would you give regarding the directory.

5.1 Question 4 Related to this I have used a piece of code found on here to send emails without messages coming up and this requires the document to be output prior to attaching to the email - I was planning to hard code this to the same directory - any thoughts or advice?

6 Question 5 Now the bit that is really confusing me is the use of INNO set up - this seems to be somewhat of a duplication is it?

7 question 6 My users are unlikely to be very competent with IT and I will only be available for telephone support. It needs to be very simple throughout - anyone got any pointers in terms of keeping this very very simple for the users who will probably download the file from the internet or receive vis a zip file on email.

8 Slight asside anyone had experience of using "Keyed Access" in a package solution


Am I missing any steps because I am having real problems getting this to work and my frustration is that my program is ready and I want to get it to some people to test.

I have searched so much I am totally confused on this and apologise if this seems really silly to those of you that are experienced in this and thank you for taking the time to read.

 

[CJ_London]

Re 64/32 bit - if your access is 32bit that is what will be packaged - the bit of the machine is irelevant

Q1 & 2: you should convert front end to accde - accdr is only for testing a runtime version in a non runtime environment. Any user with a version of access can change the file extension and gain full access to accde

Q2 if some users do not have full version, they will need to install runtime, however be aware that runtime does not have a number of features you may be relying on for the system to work. For example they will not have access to the ribbon or shortcut menus. Before distributing you should change the extension of your development db (or a copy) to .accdr and run it to test

Q3 Consider creating a folder in the localappdata folder and putting files there

Q4. no idea

Q5 - you'll need to read up and understand more

Q6 - ensure your error handling is top notch and gives sufficient information for the user to tell you what and where the problem is. Include a pdf manual and/or videos to explain how to use the system - or links to your website. Ensure you have your versioning maintained so you know which version the user has

I don't have experience of Keyed Access but if you search online you should find plenty of opinions - I think there are a fair number of posts about this on this forum

You say your program is ready, but you haven't split the db or debugged it yet, and by the sound of it, you haven't tested in a runtime environment yet

 

[humph]

Yes many thanks CJ - Ready is a relative term - ready to test and do my best to ensure that everything works the way it should.

Regarding the ACCDE I have tried this and got the error message " Database cannot be opened because the VBa cannot be read". Hence the post and the query about am I doing this correctly - any thoughts on that one?

 

[CJ_London]

not sure what you mean - you have tried the accde?

To create an accde file you need to compile all your code then save and publish to make ACCDE. Then open the accde file to package and sign

 

[humph]

Yes I had tried to package it and install on another machine without Access loaded ( using runtime ) and got the error message. I also note your step re Package and Sign - is that an essential or optional step. and where does it come in the process.

Thanks for your help with this and I hope to try again later this evening.

 

[CJ_London]

is that an essential or optional step. and where does it come in the process.

It depends on how you are distributing, you can just send the accde file (plus other files as required) zipped up or you package and sign everything which provides a file the user executes to unpack everything. It is the last thing you do before distributing.

Note the user still needs to install a 32bit runtime if they do not have the required version of access. If they have 64bit office you need to supply a 64bit ACCDE.

I note you are developing in 2010 to create a 2007 version. This is potentially an added complication - not sure if when you make the accde file it doesn't convert back to 2010.