Question What Access and Other Programs are needed

[mbc]

Hi,

I hope this is not going to bore you guys to tears, I have a specific line of questioning I would like answers for. Your expert advice will provide me with the direction I need to go for the next 12 to 24 months.

I am wanting to know what version of access and the associated programs I will need to redo an existing project to bring it up to today's modern look and feel.

I previously did an application in Access97, and at that time I also needed to purchase a program called Office Developer Edition Tools to enable the program to be installed as a runtime on client pc's.

I am not a programmer, but a really good hack. The program/application I developed sat on the shelf for a number of years due to personal reasons but I re-entered it in the market about 3 years ago. I am now seeing around at least one sale a day and the interest in the program is increasing, so I expect to see the sales increase well beyond a sale a day in the near future.

I now feel after many changes and updates to the program over the last 24 months that I have exceeded the limitation of the version of access it was created in, and as the success of the program is not something I want to give up I feel its time I change to a later version of access and redevelop the application.

I was never able to successfully import the code into a later version because it was written in access 97, however even if I could import the code there is so much that needs changing from what I have gained from client feedback over the last few years that its almost necessary to simply start again.

Over the years I have seen so many versions of access and heard so many people screaming about the poor quality of the program and the problems they were having with individuals loosing information that I am now needing your expert advice as to what version I should use.

My application is sold as a stand alone program, it is for business use, and holds critical small business information, hence it cannot loose records or data.

As I mentioned I am not a professional programmer (I am a self taught hack), which is why I like to have the tools to take care of everything for me. I am prepared to put in the work and learn whatever version of Access I need to. I previously burnt the candle and only got about 5 hours sleep a night when I first developed the program so I can do it again if need be.

So if you have the suggestions as to what version of access I should be looking at.. I need stability as the software I develop holds small business information which cannot be lost due to unstable access. I cannot have a version that is prone to losing records.

I know access has most likely come a long way but some of the versions after access97 were so unstable that I stayed away until now.

Also I will need to know what other software is going to be needed to take the application into a complete installation file to enable successful installation on another pc, with its own copy of runtime etc (if we still call it an access runtime version). I don't want to have to hack too much, I would rather just purchase the program and have it all done for me.

I run XP on my machines, but I will go to windows 7 if need be.

The completed application/program will need to be able to install and run on XP and above, and bit 32 and 64 if this is possible. I know that many users of my software are running my application on windows7 64bit with no problem, but it never worked on any other 64 bit system, and of course it was not really suppose to as it was a 32bit program design.

I will be looking forward to hearing what you have to say...

thankyou, and happy new year...

 

[Dairy Farmer]

Check the link in my signature. It tells you all about Access 2007 Runtimes and Deployment Tools.

They are now free for 2007 and 2010. So choose your weapon of choise.

Runtime (as you know) allows the app to be run on a computer without the need for Access or if the computer has a "lesser" version.

The deployment tools adds a new option to the Access menu button. This allows you to make an install of the app. It gives 3 options: Run with Access, Run with Runtime (user must have Runtime installer or it will download it for them), and (my favorite) Run with Runtime (include Runtime installer with app). All you do is download the file and include it in the install. Deployment tools is very, very, very easy to use.

As far as the data. If you are going to "upgrade" Access to 2007/2010 then upgrade the BE (back end) data files too to .accdb (the mdb version in 2007/2010). This can be done at the very end and you won't loose anything. Obviously you will make backups.

The FE (front end) upgrade may be a bit of work. It all depends on how much code there is and if this code translates correctly. Have a fiddle with 2007/2010 first. Just open the app in 2007/2010 and convert it. Remember to add the path to the app to your Trusted Locations or the code will probably not wiork at all.

One thing that may take work is the menus. Office 2007/2010 uses a Ribbon rather than drtop down menus. IMO it was a huge leap in the right direction (bracing for the flame war). But you app can inclde the Ribbon or not. It is your choise. I find the lack of the option to change the height a bit of a hassle and my current project has no Ribbons at all. Just a full screen of app.

Anything I missed chaps?

 

[mbc]

thanks dairy farmer,

I am realizing this is going to be a huge task. I am not even expecting 2007 or 2010 to upgrade the data or import any of the code as the earlier versions before them could not do it, but maybe these can.

Almost all of the application is code, no drop down menus, the client sees nothing access related and most likely doesn't know it is even done in access, I use my own screen icons which carry out the relevant code when clicked.

I am not able to see your signature links as the forum requires me to have made 10 posts before I can see your links. Which doesn't make much sense to me as it means I will have to find some post somewhere where I can be and idiot and make stupid responses....

But it is interesting to see you mention about the runtimes an deployment tools being free.

I did some research on microsoft products last night and I kept coming back to visual studio 2010 as being needed. But maybe this is for implimentation and inclusion of the other programs with access, such as word... But maybe I have this all wrong..

I will look for a post where I can spam, unless you can repost your signature links for me...

thanks

 

[mbc]

hi dairy farmer,

I looked at your signature from you profile.. thanks.

I just want to understand one more thing, sorry to be painful..

You mentioned this:

The deployment tools adds a new option to the Access menu button. This allows you to make an install of the app. It gives 3 options: Run with Access, Run with Runtime (user must have Runtime installer or it will download it for them), and (my favorite) Run with Runtime (include Runtime installer with app). All you do is download the file and include it in the install. Deployment tools is very, very, very easy to use.


Just so I understand this right, I know time changes so I have to catch up. But are you saying that the deployment tools are actually part of 2010 access, so all I need to do is select it from the menu and I can have it create an installation of the application ?

Is this an executable file, to enable a full installation of the application and the access runtime (if it is needed).

thanks again

 

[Simon_MT]

Personally, I would upgrade to Access 2007 first and see how much there has to be done to fix problems from upgrading from Access 1997. There is nothing unsurmountable.

Allen Browne has tips upgrading to Access 2007.

http://allenbrowne.com/Access2007.html

I agree with Dairy Farmer don't concern yourself with Ribbons at this stage when Menu based forms will suffice. Access 1997 was a fantastic solution, Access 2007 also makes a quantum leap particularly the User Interface.

Simon

 

[mbc]

awesome, thanks for the link Simon.

I think you and dairy farmer have convinced me to go to 2007, it sounds like that is the version to look at first.

The more I think about it I realize that if a huge chunk of the program can convert from 97 to 2007 then I only have to make changes to the existing format and add the new features I want to put in, this will save a lot of time. The more I think about it the more I realize that there is a lot of work in redoing the whole lot, it is surprising how much time was spent on the project, I guess all told I have spent well over 3000 hours on the project and I think that is conservative.

But I admit it took some trial and error to learn what I was doing. If I have to do it again I will, but at least this time I know that all the time will be repaid in the end, where as originally I just put the time in and hoped for the best.. .

thanks

 

[Dairy Farmer]

Sorry I should have said DEVELOPER. Here is the link.

http://msdn.microsoft.com/en-us/office/bb229700

You need to download both Runtime and Developer. Installing Developer and you will have the option in the menu. See the 2 screenies.

 

[mbc]

thanks dairy farmer

Its all making more sense now