so i buckled down and bought the developer extensions. this has been very good, but there have been a few drawbacks.
drawback number 1:
when the user opens the program, they receive all sorts of security warnings. i can't turn this off from inside the deployed program, and i can't figure out how to turn it off on the development end. i know i just need to go into security and set the macro warning level to low, but it won't let me. the program has worked from here, but this is highly annoying.
drawback number 2:
i don't know how to have the users update the program without having them completely uninstall their current one and reinstall the new one. i know there's some kind of update key and product key (both of which i wrote down), but i don't know how to make an executable "update" program (kind of like the way video games update, with patches and whatnot).
drawback number 3:
in order to have the program connect to the server, i need to load the program first onto the server as an mdb, then use the developer extensions on there once i've relinked all the tables (i don't have an S: drive). is there any way that this can be done automatically (link to a drive that isn't on your local machine)?
feedback/suggestions to any of these are greatly appreciated.
I will have to deploy my access application that I have built with Access 2003 english version on an Access 2003 French version. I wondered whether there could be a problem because of the difference of the language?
I have a problem with my DB once it gets deployed. I include the Access runtime using the Deployment Wizard but when we install it and open the DB it give us "May contain harmfull Macron. Please install Jet engine 8.0" Then it continues on to say "the application may contain harmful macros do you wish to continue?" we say yes but still no luck. We updated the jet engine but no luck there either. The DB opens but some of the code that brings up pictures on the "on load" event, isn't working. It works on computers that have access installed but not on the Run-time installations. Any suggestions. You guys have helped so much in the past to get me this far in my Access career and this one needs answered quick.
Hi guys, I hope somebody can give me a quick step-by-step.
I've nearly completed a program written in Access and have started to venture into marketing the program to a local company. When asked what other modifications they would like to see i was sent an email stating;
"A major item would be to deploy in MS SQL. You should be able to do that free of charge with the low tier version of SQL."
I had a feeling this would come up, but I don't want to sound like a total idot when talking to these folks... I really have no true understanding of what they are asking, but I suspect it refers to conversion from jet. Question: Is this a reasonably easy modification? What do I need to purchase? Would I be better off telling them the program is 'as-is'? Can this be easily done by someone who has never done it before? I'm sure other threads addressed this issued but I would truly appreciate a full understanding of my specific problem. Thanks, Scott.
Hello, I have finished a program with ACCESS 2007 (VBA) at work. Now, my boss wants his employees to use it from different computers. What would I have to do to make this work?? I suppose ACCESS has a runtime version or executable that I can install on every computer of the company? Or do I have to install ACCESS 2007 on every terminal (which would be very bad by the way)?? I would appreciate it if somebody would give me a hand on this since I have never done this before.
I have Office 2000 Developer installed on my workstation at work and need to create an executable to deploy to other workstations that do not have MS Access. I'm using Access 2000 and the few that have the runtime installed already have Access 97 runtime.
When I execute the Package and Deployment Wizard I click on the checkbox for "Include Access Runtime". When it creates the package, however, the runtime is not included. I have verified that the runtime is on my hard drive. The CAB file is only about 10 Mb - the same size it was before I tried to create an executable that included the runtime module.
Any suggestions on what I am doing wrong? The size of the module created by including the runtime is not a concern at this time. I just need to get this application deployed for a mission-critical analysis task.
I have followed the very informative postings here on security and deploying a multi user access application and have started doing that myself. A lot has worked but there are a few things that are not working out right and I just wanted to get some clarification on that. Hopefully this will benefit others in my situation as well.
1. First, I put security into the database by creating multiple users some with Admin and some with user priviledges.
2. I created a different workgroup file (product.mdw)
3. I then split the db to front and backend. I used UNC to nk tables from FE to BE
4. I put the BE on a shared network folder along with product.mdw. The reason is I am still developing the app and may also need to tweak the user permission settings, so thought of putting teh .mdw file on a server rather than putting it on each users machine for now. I am then using a shortcut on each user's machine that references this .mdw file on the server
5. I also have the FE on the server for now and created a shortcut on each user's desktop (I am doing this for now so that I donot need to put the FE on each users machine every time I change something. this is temporary for a few weeks till I finish development. After that I plan to put the FE on each user's machine)
The problem I am facing is that after putting the shortcut in a user's machine, if the user even wants to open any local Access db on their machine (not my app), it is now asking for a UID and passwd.
Now, when I put the shortcut on the user's desktop (to repeat, I referenced the FE, and .mdw file on the network folder in the shortcuts Target settting), should I have done anything else on the user's machine. After just putting the shortcut on the desktop, the user could click on it and go directly into my database without any UID and passwd though I have security in my db. The I went to the user's Access install and changed the workgroup file to the one on the network folder (through Tools - Security -Workgroup Info ...). Was that necessary because I had alsready put in all the necesary parameters in the shortcut's Target setting?
I guess I am missing someting about how the .mdw file associates with Access. When you define a .mdw file in the Tools - Security - Workgroup ,..) setting, does that associate with a particular DB or for any db that this Access install brings up? If so, then how does one get aorund the problem of deployment to user's desktop where the users could be having their own local Access DB's that they use without a password but need to use a password to access a DB on the network. I cannot imagine that because I require the user to use a password for my db on the network means that I have to tell them that they need to use a password for any DB they use in their machine from now on.
Please let me know where I am going wrong. Thank you
I've designed an access ade file (based on sql server) and distributed it at the network.
Somebody else has made another database (mdb) and placed the users in a access workgroup file by placing their windows logons into the workgroup file. These users happen to be the same users accessing my application. The following thing is happening : "when the users open my database they are prompted their user names and password of the workgroup file'.
I placed an empty database and the same thing is happening, the workgroup security is active alongside every database deployed to this specific user group.
How can I easily 'tell my database' it shouldn't make use of the workgroup security?
(It's odd that an ade which isn't able to use workgroup security prompts users by using workgroup security)
Some time ago I saw a presentation of access 2007. It got me very enthousiastic. But before I start working with it I want to know if it is possible to deploy Stand alone applications I am gonna build in Access 2007? And how???
Apologies if this has been covered before - I promised I have searched and not found an answer.
I have just purchased the Access Development Extensions so that I can deploy my database's to users without Access. So far, I've managed to create an intallation file fine. Hwever, the database is to be used by multiple people and needs to be split.
If I create the runtime application of the frontend, all of the tables point to the backend on "my computer". I then need to give it to my client who will store the backend on thier server. How do I then make the front end (all locked becuase it's runtime) point to the backend in the new location?
I hope that makes sense.
I'm supposed to be installing this tomorrow, so any help would be much appreciated
I have a database that I've split and have deployed to 7 persons.
The thing is, I have three (3) forms:
Form 1 Form 2 Form 3
...that require changing a portion of a line in each form's respective VBA codes. I need to change the directories to where an excel workbook is stored after exporting, and another is where same excel is moved to after being uploaded.
At the moment, during deployment I have to manually change the directories.
I was thinking of maybe a pop-up form with four (4) fields that allows the user to select his/her name at the start-up of their frontend app, and paste the directories in the other text boxes provided.
This information will then be used to replace the directories in the VBA.
If I were to make changes and have to redeploy, I would have to do everything manually again.
my post at www.thescripts.com was deleted. It seems they don't really want a true deployment solution help to all ms access developer.
Ms access is a true king RAD DB frontend dev't. tool but the deployment of the finish apps are very unstable.
Sagekey is almost there, but I want to make a single EXE on my Access Apps that run even on the usb flash disk.
I have already found the solution, perfectly done! using one of the tools available in the web. but I will not post it again, I'm afraid this post will be deleted again... I hope this forum truly helps.
