Deploying DB To Users! (mde, Self Installation, Update User Version)
Feb 8, 2006
I have a db with more than 100 forms, reports - objects. My backend tables are linked sybase tables. What is the best way to hand this over to the users?
1. I want to create a mde version (which is not working, here's my problem :mad: Failure In Creating MDE File (http://www.access-programmers.co.uk/forums/showthread.php?t=94465)
2. I want a way to send this application to the user, in order that is installs on their desktop or a location i specify on the user's drive. I have no clue how to accomplish this, but i know that when i download some applications they do end up on my desktop :rolleyes: , so they must have done it somehow. Please help?
3. I want to have a master mdb hidden on the network somewhere, and when i make changes to that (e.g. my form or reports). And the next time the user goes into the version installed on their drive, it checks for the last version of the front end, and if that's not it, it erases the old one they have and installs my new version for them automatically. I know this can be done. Can you help me?
I'd really appreciate if anyone can help me please in any way. Advice, links, tutorial, whatever. Many blessings will come to you!
Ghudson! Before you attack me, i've done a search on the forum and though i've seen some posts, i can't seem to find one best for my means :) Thanks!
I have created a DB which has a front end which is linked to a backend where all my datas kept.
I want to install my database via cd-rom using and install wizard. If i ask the install wizard to c:/user/programs/ would i have any problems with the links between the front end and back end?
If i would how a problem with the links to the front end how would i cover come this?
I have created an access 07 database and split it to a back-end and a front-end with linked tables.
I wish to deploy it an a network of 4 computers, 3 of which are running on XP. The back-end will be on a computer running on XP. Now, from the instructions I have come across online, the Back-end has to be located on a folder where all users have Red and Write rights!!! And I am thinking, if the users on this network can actually see the back-end since it is on a shared folder where they have all the rights, then does that not compromise the security?
Is there a way of linking to the back-end on a network WITHOUT the users being able to access the back-end?
I have a very simple Access database that contains a form where users enter sheduling information...I wish to limit a group of users to be able to read this information only and not modify or add to it.
The tables are in a back end mdb. The rest is in a front end mdb. And the users actually use the mde file when working with the schedule.
What in your opinion is the least complicated method for providing some users with the ability to add/modify and some with read only.
I have been trying to set up a batch file to allow users to copy the latest version of the front end whenever a change is made. The following is the code that I am trying to get to work properly. The first part works fine, the old front end is copied to a folder on the user's desktop as a backup. But I cannot get the copy of the server - the "P" drive, to overwrite the current copy on the user's desktop. Actually I cannot get the code to copy the new front end from the server and install it on the user's desktop. I think the path is correct for I seem to be able to run the new front end from the server.
When I look for the location on my computer, the server locations is listed as:
General (Servernamefiles) (P: ) (there is no space after the P: it seems to result in a smiley face when I type it and try to post it).
for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set year=%%c for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set month=%%a for /f "tokens=2-4 delims=/ " %%a in ('date /T') do set day=%%b set TODAY=%year%-%month%-%day% rem echo %TODAY%
[Code] .....
This code works so I thought that the path was correct rem this works rem start the new DB front end Start P:AccessMainSplitBENewFrontEndDBMain.accdb
But this code does not. echo f | xcopy /f/y/ P:AccessMainSplitBENewFrontEndDBMain.accdb c:UsersUserNameDesktopDBMain.accdb
Neither does this: echo f | xcopy /f/y/ ServerNamefilesP:AccessMainSplitBENewFrontEn dDBMain.accdb c:UsersUserNameDesktopDBMain.accdb
Got a problem here with Access 2003: got 36 categories (example: volume from 0-0.1=category 1 vol from 0.1-0.2=category 2 etc) and a whole bunch of records (in a table) stating volume per record (0.111, 0.23456 etc). For each record I need to know which category it is. Now in order to prevent me from writing 36 update queries for each category (if vol>0 and <0.1 then category = 1 etc) there must b a smarter/faster way to do this. What is it?
I run a multi-user system of over 200 users. The only facility I have for advising an office-wide logout is required is the email system. However, staff either don't read their email or forget so I have to run around like a headless chicken trying to get everyone to get out/stay out of the system while I perform maintenance etc. Is there a way to enforce a logout and keep users logged out until a requested time without spending a fortune on new software? Any advice would save me a lot of hair pulling (not mine :)).
I have a database originally was created for 1 person to use. Now, this database has to be shared by various people in the company over a network. Some are only allowed to view reports while others are allowed to make changes to it. How can I convert this database to a multi-users one, and maintaining its data integrity? I can possibly restrict 1 person to use the database at any one time. I know it's not going to be easy, but with the help of you guys I am sure it can be done.
My search was snowballed with lot of results about dealing with split database, seeing who's online, etc. so I'm not sure if that is a good idea.
I want to make a table of Users because my users may need to put their name on some of reports, so I could use CurrentUser() to figure out who's who and put down their proper name after comparing the username via a query.
However, I'm not sure if it's possible for me to link the user table to the user groups of database to ensure that there's no ghosts or users that doesn't have a proper name to be placed on the reports or whatever. More of a validation, really.
Is that doable or maybe there's another way to do that?
Currently, I have 10 Users running a front end form that connect to back end data where they add to current records and eventually check that the record is complete.
I also have an "Apply Filter" button on the right hand side of the form that allows the user to apply filters to the records to show specific data that is not complete.
I am currently hearing that while the user is working, whether they apply filter or not, it seems as though all of a sudden, all of their completed work dissapears from their recordset hence not allowing them to go back to make changes to it if needed. I can only conclude that when a different user clicks apply filter, all users are affect some how... here are some examples of the code for the filter:
Code: Select Case [cboFilterValues] ' Where the user selects a filter parameter from a dropdown Case "All Data" strSQL = "SELECT * " & _ "FROM [Data Table] " & _ "WHERE [Complete] = No
Then it does:
Code: Me.RecordSource = strSQL
I am basically trying to find a way where only the user wanting to view the filter is affected... FYI, the other users arent actually seeing all the filters from the other user filter choice, they simply loose all their completed work from their form.
I have a question about Access runtime. We have some users at work who don't have Access on their machines, but we would like them to be able to use databases we have created. My suggestion was to purchase Visual Studio Tools for Office, which will give us Access Developer Extensions and allow us to distribute runtime versions of our databases.
However, the pcs here at work are pretty well tied down in terms of installing anything. E.g. no registry changes are allowed, unless you are an administrator.
So my question is - what is actually involved in installing the Access Runtime. Can it be achieved simply by copying the relevant files (ACCESSRT.* ?) into the office directory, or is there more to it than that. Will I be able to get my databases up and running myself, or is it likely that I will need the help of the Technology Department to get the Runtime installed ?
Hi, a colleague of mine has Office 2000 installed on her work PC in order to carry out Access datadase responsibilities (amongst other things) as part of her job.
I think (though I cannot be sure) that someone has 'locked down' the copy of Access to such a point that shift bypass no longer works, F11 does not display the database window etc. This is strange because our company generally does a default install of Office and leaves most everything configured as standard.
In short, I need to access the Tools menu to set startup screen options and customize some of other options for her. Obviously I can't.
Will this problem require a complete Office re-install or is there a way to undo someone elses changes and set Access back to 'wide-open' ??
I have packaged a 2007 db on a 2003 server. The db contains autoexec macro which: a. opens a query, b. opens a form with cmd button that returns a msgbox c. Runcode a function that calls a subroutine to return a msgbox.
Everything runs fine on server since that's where the real 2007 install is.
On my pc I have xp2 and one install of access 97( don't ask) along with office 2003 installs(excel etc, etc).
I installed access 2007 runtime on my pc.
I copied the package from the server to my pc and did install. When db finally opens the query runs, the form opens but fails on the runcode. The code behind the cmd button returns nothing. This tells me that on vb was included with the db when it was packaged or I don't have rights to run it? Either why how can I resolve this issue as info on subject is nill.
Twice a year, a database of mine is accessed and put too use by various staff within a time range of 1 week. the database is on a shared drive and in a location which can be accessed by all.
The staff access the database from different workstations and in some instances at the same time.
This has only led to issues in the database being copied and then confusing staff on what database to click on thus i have 2 databases which i then have to sift through and copy/paste into the correct one.
I want to know the best way i can:
1) Prevent multiple users accessing the database at a time. 2) making a copy of the original and typing into a separate database.
I’ve read most of the posts on splitting and deploying Access applications but most of them appear to concentrate on networked backend databases. However, my case is slightly different and I would like somebody to confirm that I’m taking the best course of action to achieve my goals.
I’m currently developing a non-networked accommodation booking system which has some basic functionality that my end user is testing on their standalone PC. I am currently adding historic data to the data tables to allow the end users to make full use of their existing data when testing the new system. The application development is ongoing and I will be releasing updated versions of the system over the coming months and want to be able to release the new features without having to reload the most up-to-date data from my user each time.
Therefore, is the best approach to:
Add the historic data to my development. Split the Database giving front and backend databases. Initially deploy both front and backend databases to the end user. Continue with the development on the split system and when new features are added just deploy the front-end database to my users leaving their data tables in tact on their machine.
i have an access application with a navigation form to browse through different forms & reports.i want to know how can i use it over my lan network as an intranet website ?can i convert it simply to html interface or what ? i know about access runtime but if i want to deploy it into intranet ( i.e. browsing through web browser ) what r the different methods?
I am using the Packaging Wizard of the MS Office Access 2003 Developer Extensions. I would like to change the Root Installation folder to a customer Folder. However, I am limited to the list given (Program Files, Documents & Settings, etc..). I even tried to see if I could change the INI files produced by the package, but could not find any reference to the root installation folder. Does anyone know how to change this, either through the wizard or manually.
I know I can have the user move the folder once the install is complete, but I do not with to do this.
I have to do this and I believe there is VBA code to re-link tables when needed that can be found on the web. My client needs access to everything because he will move on to another developer after this, so what I thought I would do is send him a private file that has the password for the backend and then just write the ADO code needed in the app's front end to connect with the password.
We have an access database stored in a shared location. One of the tables in the database is used to record transactions made in an excel spreadsheet-this is done programatically using VBA and SQL.
So here is my silly question; If users don't have access installed locally will the code be able to write to the shared access database?
I have a split DB accessed and updated by several Users. How can I limit the update of one table to only one User, administrator if you will. :confused:
The Database is not split. Have 30 some users. Here is what I am trying to do.
I have Mary, Sam and Bill logged into the database.
When Mary signs in she has no records to update, but when Sam and Bill logs in they have records to update.
How can I get a message just to Sam and Bill, but not to Mary?
I have a qry what records needs to be updated.
Just how would I go about this? I thought I had it when I use the "environ" but that just shows who is logged in. I am sure the form has something, but I haven't found out where.
I am running a access db within a company with about 40 users. I have split the db for multiple users. The only way I have found to fix this problem is to ask the user to close it and reopen it but this is just a quick fix.
Is this cause by our Microsoft servers or is it cause by access. Any help would be great :D
Here is the complet error msg
Could not update; currently locked by user "Admin" on machine 'XXXXXX'
please note that the user is not logged on as "Admin" but as normally user without admin rights.
I have done some searching to find a method for logging & timestamping when users log in and out. I have no problems with capturing the Log IN information my problem lies with the log out portion where I am trying to use a Update query to update when the user logs out of the database:
I can get the update query to do what I want, but for some reason it is creating a duplicate record (exactly the same as the last record updated)
Here is the code I am using:
UPDATE LogInTable SET LogInTable.LogOutTime = Time() WHERE (((LogInTable.LogOutTime) Is Null) AND ((LogInTable.UserName)=LogUserName()));
Basically I am trying to tell the Query to ONLY update records where the "LogOutTime" is Null AND where the UserName field in the table = the username of the person trying to run the update query.
Please help I can't figure out how to prevent these duplicates. :(
I want to create a form that allows users to update multiple fields for multiple assets. Below is what I came up with:
Ideally, I'd like the subform to be filled in by having the user select multiple Assets from the S/N combobox field which would then auto-populate the "Type" field. Then they would fill out the appropriate fields they want edited in the top part of the form. They hit save and magic happens. This would also be nice because only assets they want edited would be displayed (easier on the eyes) and no distinguishing would be necessary. To do it this way, I know I would need to use a temp table but I wanna avoid using temp tables.
I know I can do this by adding a Yes/No field in the "Asset" table, setting the "Asset" table as the subform's recordsource, and then putting a checkbox in the subform and allowing them to check the assets that they want to edit (which would also allow me to sort it instantly so that checked Assets are at the top of the datasheet for easy viewing), but I would like to know if there's a way of accomplishing this without the use of checkboxes.
I know I could also use a listbox and that allows them to multi-select items, but I'm not sure if that allows me to group all selected items at the top of the listbox for easy viewing of selected items. Plus it would involve a lot of scrolling (there are over 2k assets).
