That would do the job nicely, but I think I might have been able to make soemthing else work. Tina suggested earlier that I use a query to get the information from the form to a table. Teh table would then be used to display the information in a report.

If I do this:

It should accomplish the same goal. The question now is which is better?

I know this works, but can you forsee a reason that the other code would work better? I'm asking because I'd rather make the best program I can so that noone has to do maintenance on this.

CarsonJ,
Here is my two cents on this.

Excel really not a good option for this many people to share the data. A multi user application would be so much more productive than Excel.

If this were my client I would build an Access application. No Excel needed. This would allow lots of workflow to be built in.

To deploy the front end to 250 people (desktop) cost is $0 with a potential savings of over $37,500. What? How can that be? Use the free Access runtime. The saving comes from not having to purchase Excel.


The using a properly normalized database will help reduce future support maintenance. Using Excel will probably guarantee a lot more future support and maintenance that is done in Access.

If the Access application is well design the user will not need to be very skilled with Access. This is not true with Excel.

Access runtime sounds like a good option. I hope you'll consider that. What version of Office are you using right now?

To answer your question, that type of code is okay if you just want to dump something on a speadsheet. I think it's the same as just clicking up an export manually. It's fine if it satisfies your requirements.

We're using Office 2007. I like the option of using Access Runtime. It would not only keep everything "in house" but it would also make it so I didn't have to figure out a way to prevent changes from being made by "unauthorized personel". I've presented thsi to my bosses and am currently waiting to hear back from them and IT before I can go ahead.

If I do get to go with Runtime, then the whole thing would simply be making a query to store the information in a table and then create a Report to search through and display the table, right? I say simply but there is a bit of work in there. I could actually reuse the whole process I have been working on to get the info to Excel. Instead of dumping it out fo Access I would keep it in the table and work with it from there. I think I'm on the right track.

Thanks for the ideas, this should be a lot less finicky than going to Excel.


You got me there, but the point is that I want to create the most user friendly program given the restrictions placed upon me. That really is what everone wants for their programs.

-CarsonJ

You're welcome. I have never used runtime myself.

I think you are seeing the benefits of using Access. I find the Access runtime really helps to reduce software costs.

The may also help:
What is the Access Runtime Version?

Access 2007 runtime deployment - FAQs

That it does, my boss approved the idea, though IT hasn't gotten back to me yet, so I will be moving forward. Since I have been working in another sub-forum to get the query to work properly, all I have left to figure out is the report. I'll start a different topic in that sub-forum if I need some help (9 to 1 odds that I will).

Thank you Tina t, HiTechCoach, and projecttoday for the great advice and helpful tips and links. You all really helped me understand more about Access. (IMG:style_emoticons/default/thanks.gif)

-CarsonJ

CarsonJ,

You're welcome. I am glag that Tina t, projecttoday, and I could assist you.

Good luck with your project.

(IMG:style_emoticons/default/uarulez2.gif)

you're welcome, hon. i'm glad the guys stepped in and gave you some suggestions that will really work for your situation - UA is tops! good luck with your project, and come back to the forums anytime you need a hand. :) tina