General :: Deploying A Database Without Users Seeing Back End
Jul 30, 2013
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 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 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 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 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.
I plan on using Excel as the front-end and Access as the back-end only. (all queries and forms are in Excel). A single Access database will be queried from multiple Excel files that will be located on the share drive (Linux server). Access tables contain memo, text and number fields. Data will be sent to Access tables and records will be appended/deleted; all via Excel.
There will be multiple users interacting with a single Access database via multiple Excel files located on the shared drive. Users will be interacting from different workstations with Windows 7, all have Access 2010 and Excel 2010 installed.
This process works for me from my workstation but I am not sure what will happen when other 4 people will be sending/appending/deleting records to the same Database? How do I make this work? What settings do I need to check in Access to make this possible?
I have a database which is split so that several people can have a 'front end' to the database to access one common back end. This works fine on a network but I thought I could load the backend up to my webspace and then with the links manager point to it, but it doesn't work. I get an error report of 'not a valid file name.'
The website is [URL] .... and the backend database name is Probus_data_A.accdb and so I entered [URL] .... as the address in link manager.
So i want to protect the back end of a database but im limited to what I can do....I am unable to restrict members from accessing the file by username...I am unable to place it in a local area which is pass protected...I am also unable to encrypt the back end as the front end needs to be able to access it (and I dont know how to allow it to do that...)
I am trying to use VBA to backup the BACK-END of a split database (so I can automatically archive selected data). If I use FileCopy I get a message that the BACK-END database has not been found.Obviously I could 'unlink' the BACK-END, copy it and 're-link' it..Is it possible to copy the BACK-END tables(not just the links) into the FRONT-END and get at them that way?
The database: is for tracking computer issues (this part is complete), also I need to show the on call roster (mostly complete)... This will also have a time sheet that I need to be completed once a fortnight, however I would like it to auto populate the staff members logged information (I will get into that a little later).
Question 1: I do not want the users to log into the database, however I do want the database recognise who they are from their windows logon details.
I am using access 2007 and my backend DB has a lock on it while every user has said they are not in the front and back end db's. Is there a way to remove the .laccdb lock? I need to modify my backend and this is holding me up from making any design changes.
I have a split database. I have secured the mde sufficiently but I need to secure the back end so that no one could link to tables in it. If I introduce a password to the back end is this going to require those using front end to supply the password? If not then this could be good solution.
As the database is on the network drive, is there any other way to prevent people to link to the db? Can I hide the db in the network drive? Or should I hide tables in the BE. Should these still be available to be linked?
Using Dropbox to host a split database. Ulimately I would like to create a run version for users with the back end held in a drop box directory.
As an unsplit database everything is working fine on dropbox records are saved in a timely manner and great.
Once I split to FE /BE only some records are saved on the BE and some are dropped. Was getting conflicted copies of Back end but manged to stop this happening but the records were noit on either copy.
Gave each user their own FE (on a drop box directory) linking to a BE in a sub directory on the same dropbox.
The key issue is that not all users have access and I don't want them to get into code so want to aim towards a run version.
I have developed a new database using Access 2003, which I need to roll out across various users. Some have XP, some Windows 7, and each of them has different size screens. I guess I will have to adjust the various forms to size to a particular users screen resolutions and sizes.
Is there any way of doing this within the database itself, or do I have have to adjust each form according to the local users PC specification?
I used to have a handy tool called LDB Viewer or something like that with which I could see who is using my database. Now I've upgraded to MS 2010 is there a way to do the same?
I'm an absolute novice at Access. I have a very simple (yet sufficient) database that lists our company's projects, tasks associated with those projects and when to invoice.
Our company consists of myself and my business partner. We both work from our (separate) homes. Our project files are stored in the cloud. This works well. We have investigated a server in the past, but found it to be cost-prohibitive and unnecessary for our business.
Is there a way that my business partner can have the Access database running at the same time as me, and make additions/modifications? I don't know how this would work in terms of updating/saving.
I am about to allow users to access a database I redesigned for others to use.I am trying to save it as an ACCDE so they can't mess it up. The database is very very simple.6 tables each with only 4 fields or less... and none are related to one another
7 forms. 1 report. 0 queries... it's just a SKU generator.
When I attempt to save as ACCDE I get an error that reads."Microsoft Access was unable to create the .accde, .mde, or .ade file.This error is usually associated with compiling a large database into an MDE file.* Because of the method used to compile the database, a considerable number of TableID references are created for each table.* The Access database engine can only create a maximum of 2048 open TableIDs at one time.* Exporting a database as an MDE potentially can exceed this limit if the database has a large number of objects (table, macro, form, report, etc).
There is no accurate method to estimate the number of TableIDs the Access database engine uses during the process of compiling a database as an MDE.* However, each VBA module and each form uses one TableID, as a result, if the database has 500 forms, and each form's HasModule property is set to Yes, as many as 1,000 TableIDs are used."
The front end has been saved in a accde format and distributed to 20+ users. They have all saved this onto there computers and this is used as an application.The users complete a form on a weekly basis on the application and then save. This then saves into the back end.For some reason I have noticed that a few users submission randomly do not save. For the life of me I cannot understand why.All users have saved them into the back end in the past but every now and then submission for users do not save.
I have a Access data base (2007) which i splitted and store the back end database in a file server where all users have full control and the individual copies of front end put in the users computers. Unfortunately when one user is using the programme, others can not use. Following error msg appears. Both back end and front end are running under shared mode ( not exclusive ).
"Could not use xxxxxx_Be.accdb; file already in use."
I have designed a split database( with back end and front end), I am just wondering what would be the best way to put a password for both of the back and front end.
Is there away in which I can protect an access 2007 database modification with a password.I'm doing this because I would like to prevent my client from modifying or having acces to the database's back end system (db), I would just like him to use forms and nothing else.
I have included some code to disable the access PassKey (holding shift down as you open the database so that the database window appears). It is password protected and it works pretty well for normal users.
However, I have realised that even in this restricted mode you can go to File-Options-Current database and enable Access Keys. This then lets you open the database window by pressing F12.
My question is, is there a way to absolutely stop anyone from ever viewing the database window at all? All my code is password protected, but I still don't want an ICT person fiddling with my tables and queries!
I am using Access 2007. My boss has given me a project to create a tool for our team. I'm done with most part of the project, but for the last part I want editing and updating of database restricted to a few members of our team. However others can access the database and run queries etc. through buttons on a form.
I went about creating a login form for users to get access to the database and in turn created a table with fields UserID, UserName, UserPW and a yes/no field titled IsAdmin. For those who would be limited access would log in as 'Other' user and same as password. I am then using the code to determine if the user should be treated as admin or not by looking up the IsAdmin field in the table. Following is what I have so far, but it needs correction some places and I can't figure where:
Private Sub cmdLogin_Click() Dim xxAdmin As String 'Check to see if data is entered into the UserName combo box If IsNull(Me.cboUser) Or Me.cboUser = "" Then MsgBox "You must enter a User Name.", vbOKOnly, "Required Data"
