Access runtime 2007 and 2 front ends

[KristenD]

Two Questions: I think I am over complicating things with my database. If I have IT install Access Runtime 2007 on the users' computers that will have access to the database and I email them the application. They should be able to open up the database with access to just switchboard that I have set up for them correct?

Second one: How do I make 2 front ends? One that allows you to add and modify records and one that only has access to queries and reports?

I have to get this ready by tomorrow so I appreciate your quick responses!! Thank you!

 

[spikepl]

1. Not likely. There is the issue of Trusted Location. See this thread, http://www.access-programmers.co.uk/forums/showthread.php?t=226687 and check Galaxiom's link at the end.

2. In the same way as any other front end. You can code 1000 frontends, each to your liking. But that would be a support/change hell inviting mistakes. That, then, to be balanced against the effort to do some user management in the db, with privileges. Or, some Admin login in a corner somewhere, so that after login the Admin is able to change data. But no other user is.


BTW: "has access to queries and reports" Why do users have access to queries? The means for user interaction with an Access db are Forms or Reports.

And finally: Your stuff does not at all sound like "ready by tomorrow". You need to test deployment and also the deployed version in situ, prior to any roll out.

 

[KristenD]

I did not email the front end. I had IT install the runtime and then had put the front end application up on the server. It is being tested for the next week and am waiting for feedback regarding what the users need and want.

They wanted access to the queries to be able to export them to excel. So when they open a query, it asks them do you want to export to excel.

I should have been clearer...the db is not ready for true roll out yet this is just the "beta" testing. This is my first development for a database so everything that I have done/am learning is through trial and error and of course this awesoem forum!

Thank you!

 

[spikepl]

Your response is not clear to me at all.

1. You have nor commented on Trusted Location at all.
2. What is your frontend doing on the server? Is that simply as a means of distribution or is it run from there?
3. Your answer concernng quereis is confusing to say the least. In Access you can present data to a user in form, and you can provide facilities to export it. Whether the form's data stem from tables or queries is immaterial. But showing a naked query to a user is inviting trouble, because data is not protected there, unless eg dbOpenSnapshot is specified. From your answer it is unclear what exactly you are doing. I seem to recall bringing this issue up in another post: not to show naked queries to users, but you did not react to it there either.

I don't know what your db is doing, but an in-situ test of a runtime version in another network location than yours would verify that at least at that location all the system parameters are handled properly: backend location springs to mind as a possible issue, plus a whole bunch of things like printers, drive letters .. depending on what your app does.

 

[KristenD]

I apologize if I'm unclear.

1. When the user accesses the application it has a pop up. I am not sure how to make it go away other than click ok. Is that the trusted location you are talking about?

2. It was the means of distribution as all the users have it installed locally on their desktops/laptops.

3. As this is my first time developing a database from scratch, I am learning as I go what to do. I assumed that the queries would be fine as long as it's exported and they cannot do anything to the data in the queries. Some one tried to explain how to use a form in order to do it but I couldn't make it work as some of the suggestions that have been sent to me so far I'm pretty sure would require a form. For example, instead of the parameters in the reports having to type them in they thought drop boxes (combo boxes) would be better instead.

Like I said this is a whole new world for me, never having been in this field before so all of my experience and knowledge is coming from trial and error and all the questions I ask.

What the db is being built to do is for our recruiting/hiring process. Since we are a federal contractor and we have strict protocol for our EEOC policies, we have a strict procedure for hiring. What the database is built to do is if a job site is needing a welder who can do a TIG weld on stainless steel we then go to this db pull all the information needed. First criteria would be an active employee with a craft code 102, 202, or 302 that has a rating of a 3 or better in the skill code 411 that have been rated by a supervisor. If no one shows up on that report it then it carries all that same criteria but the rated by changes and we see who has rated themselves a 3 or better. If no one shows up on that then we open it up to all other craft codes. Basically following our EEOC hiring and recruiting procedure which is to first look at all active employees, then if no one can fit the criteria we go to eligible employees and if no one fits the criteria then we have to go out to the market place and put an ad out.

In a nutshell the db is performing a function of our EEOC policy so we can prove to the federal government that we are followoing policy and procedure.