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 haven't done any testing yet on splitting the database I'm working on but a question came up today about networking.
This database is going to be used by a few equipment operators to record machine readings on the manufacturing floor. There is a wireless network and we are in the process of confirming that the wireless signal reaches all the areas. The users will be using ruggedized windows tablets to enter the data.
The BE of the split database will reside on a network drive to ensure everyone that needs it will have access and it will be regularly backed up. etc.
Since there is alot of heavy machinery, there may be some spots where connectivity will be weak or non-existent while they are entering their readings.
The question is how will the runtime FE handle it if connectivity is temporarily interrupted?
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 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.
That error keeps on appearing in my application and no way to sort it out...
The error is the following: Runtime error 3734: the database has been placed in state by user 'Admin' on machine ... that prevents it from being opened or blocked.
I tried to sort it out by doing:
set db= opendatabase(database,0)
but still appearing the message.
could i solve it by checking if there is an actual opened connection before starting a new one? and in case that that there is an opened one, close that.
I'm in the middle of developing a database for our engineering group to track projects. I've got a question:
I'm using Runtime because none of our group has MS Access loaded on their system. So, I'm providing a link to the participant to download the free Runtime Software and providing a Shortcut to the database in the shared area.
My question is, when I split the database and provide the users with the front end do they still require runtime? Do I still provide them the link to download the free Runtime software and if so, do I save both the back and front end with the .accdr extension? I'm assuming that since they will have the front end on their systems individually they will no longer require the Shortcut.
The way the system is currently, it seems that only one user is permitted in the database at a time as it is locked out. I would like for more than one user to be able to access the database at a time. I've set the Default Open Mode to Shared so I'm not sure why it gets locked down when a user is accessing it.
We have an access database which 3 of us use at work. All 3 pcs use access runtime to modify the database records The problem we have is that when you try to open the database with pc3 it just does nothing if pc1 or pc2 has the database open. So we both have to close it and let pc3 open it, then we have to reopen it.
Has anyone else encountered this problem?
The pcs are all configured the same way, are the same model with the same Windows XP Pro image on them.
:confused: I have read a quite a few threads on spiting the database. My database is 50 Meg and running very slow. I have compacted and repair, still the same. This just happen all of sudden. Could that be possible?. What should I look out before I try to spit it?. It’s given that I will make a backup. I am running Access 2003. I have over 150 users.
I am almost at the finishing line with a great deal of help from here. I have now normalised the tables, built complicated queries, forms, reports, all from scratch as I knew absolutely nothing before I started with Access three months ago. I have compacted and repaired the database using the wizard, and also complied the code and analyzed all tables, forms, queries, and reports and relationships. The final step is to make it an MDE file so that it can go on the local network at work (not on the internet). My questions are these;
Do I need to split the database into front and back ends?
If I save a copy of the original MDB file and then make it a MDE file would that not suffice in making it run more efficiently?
Can a split MDB database be made into an MDE database?
I have a database that resides on a file server share. I have split the database to create a backend. I then posted a shortcut of the front end to the desktops of two users who have access to the share. I then tried to access the front end from the two machines simultaneously. It opened on the first PC but not the second? When I viewed the server share it had a 'padlock' icon?
Where am I going wrong? This is the first time I have attempted this scenario!! Thanks in advance, Phil
Should splitting only be done when all tables,queries,forms,reports, etc. are done. Or can it be done anytime. I am almost to that stage but didnt want to jump the gun and run into problems later on.
I was having a discussion with Rickster57 concerning my newly developed database, and he recommended that I split it so that it has a front end and a back end. Rick listed a number of very good reasons for doing this (so I will definitely do it). But I wanted to pose the question so I could get some of the reasons the more seasoned Access programmers have for creating a front and back end to their programs.
I recently split my database and also used Bob Larson's Autoupdating tool. Everything appeared to be working fine until a few users were unable to access the db. I later found out that because they are at a different site, they don't map to the server that houses the database BE. However, even if they manually map to the correct server, they are unable to bring up the db Form. They get an error stating the BE "...is not a valid path". My questions are:
1) If I were to copy all the files (the Master FE, BE, and MDE) to a public folder that ALL users have access to, will everyone be able to bring up the database Form?
2) How would this affect what was already set up when I ran Bob Larson's utility (or even the splitting and MDE creation)?
3) Is there a way to "Undo" what was previously "Done" to this database (ie: Splitting, Larson Utility, MDE creation) in order to correct the issue, or do I need to start from scratch and split the database while it's on a Public drive.
I hope this makes sense. Thanks in advance for your help.
I just want to know that " How to split the Access database in Front End and Back End application"? I am creating a database that i want to store on server and simultaneously want to give access to 20 terminals (cleints) to access the database.
Secondly, I have to provide a field in a form "Document number". However as per the requirement user can enter "PIR No", "Serial No" or at times both as document number. Both the things "PIR No" and "Serial No" have different format types like "PIR No 001" and "Srl No001".
On basis of document number later i have to give the option to search the particular document. Please guide me how to provide the option to enter the field values.
I am almost at the finishing line with a great deal of help from here. I have now normalised the tables, built complicated queries, forms, reports, all from scratch as I knew absolutely nothing before I started with Access three months ago. I have compacted and repaired the database using the wizard, and also complied the code and analyzed all tables, forms, queries, and reports and relationships. The final step is to make it an MDE file so that it can go on the local network at work (not on the internet). My questions are these;
Do I need to split the database into front and back ends?
If I save a copy of the original MDB file and then make it a MDE file would that not suffice in making it run more efficiently?
Can a split MDB database be made into an MDE database?
I'm having trouble with my database (Access 2000). I'm trying to export a file into a text file by clicking on a button. Below is the code. Where the code is in bold that is when the runtime error happens.
If i export the code manually by right click on the query > Export then this works, but for some reason by clicking on the button will not work.
Private Sub cmdExport_Click() Dim sExportFilePath As String sExportFilePath = DLookup("[DateExportLocation]", "tblSettings", "[ID]=1") ' Path if file to be exported DoCmd.OpenQuery "qryUpDateTransmissionDateAndTime", acViewNormal, acEdit ' Update dates time DoCmd.TransferText acExportDelim, "ExportFile", "qryExportFile", sExportFilePath End Sub
I create a front end and back end that resides on the lan. Front has everything besides the table which resides on the back end. Front ends table are linked to the backend. I have two computer that i am testing it on. Both of them runs Access 2003 runtime and windows has been update to the latest version, both xp machine aswell.Both has user right to read and write to that directory on the lan. Ldr exist when either of them uses access file. The strange thing is when i run a command to copy some data from one table to another one. one of the machine give me the following error "3027 Cannot Update. database or object is read only". While on the other machine it runs flawless. Another weird thing is if i modified some values in table by using forms it works great on both so i am a bit clueless where the problems is. its seems my problem is copying from one table to another. i dont have problem modyfing one table. Here is the code i use to that halt my ms access database.
Dim dbs As Database, rsProposal As Recordset, TES As String, stdocname As String, stLinkCriteria As String
TES = Me![TESID]
If TES = DLookup("TESID", "Proposals", "TESID =" & "'" & TES & "'") Then MsgBox "Proposal Already Exists for TES ID: " & vbCrLf & _ " " & TES, vbOKOnly, "Proposal Already Exists" GoTo Image264_Click_Exit Else If MsgBox("Do You Really Want to Create" & vbCrLf & "a New Proposal for TES ID " & vbCrLf & " " & TES & " ?", 289, "Create New Proposal?") = vbOK Then Set dbs = CurrentDb Set rsProposal = dbs.OpenRecordset("Proposals") With rsProposal .AddNew ![Long_Desc] = Me![Description] ![Short_Desc] = Me![Opportunity] ![Dest_Site] = Me![Install Site] ![TESID] = Me![TESID] ![End_User] = Me![Contractor/Purchaser Name] ![Date_Due] = Me![Proposal Due Date] ![Date_Completed] = Me![Close Date] ![Status] = Me![Status] .Update .Close Set rsProposal = Nothing dbs.Close Set dbs = Nothing End With stLinkCriteria = "[TESID] = " & "'" & TES & "'" stdocname = "Form Prop - Detail" DoCmd.OpenForm stdocname, , , stLinkCriteria DoCmd.Close acForm, "Form TES - Detail" End If End If
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 am combining 12 Databases. I have split all 12 between the server and the desktop. My question is “Should I combing all of the data table on the server into one database or should I leave all of the individual application data tables in separate Databases on the server”. Additionally, is there a limit to the number of tables an Access DB can handle? My inclination is to keep the functionality separated but the problem I have is that some of the functionality within the applications overlap. Recommendations!
The moment of truth finally came and I split my database FE/BE for testing only the truth was a bit sour.
Background: I have several forms in my database that have a common series of buttons at the top which open their corresponding form. Before the split, everything was fine - you can click on the button and the desired form would open. After the split, I'm getting the error message:
"Microsoft Office Access couldn't find the toolbar 'EVM Database Menu'."
This is referencing a toolbar that I used during development to help jump to forms.
I tried removing the toolbar from each form (Tools > Customize > Toolbars > unchecked the custom toolbar), and re-split the database FE/BE ends, but to no avail..
So, I checked the event codes to be sure I didn't program something wrong. There are 9 buttons total to open forms, 7 of them give this problem, the remaining 2 do not. The code for the problematic and non-problematic ones are identical!
Example - Non-Working (error message re: Custom Toolbar): ----------------------------------------------------------- Private Sub cmdActuals_Click() On Error GoTo Err_cmdActuals_Click
Dim stDocName As String Dim stLinkCriteria As String
Example - Working (no error message): ----------------------------------------------------------- Private Sub cmdPerfProj_Click() On Error GoTo Err_cmdPerfProj_Click
Dim stDocName As String Dim stLinkCriteria As String
Questions: So..this has nothing to do with code, it must be a problem in the linking somehow, right? A bug possibly? What else could be causing this? More importantly, is there a solution to my predicament that anyone could help out with? Searches so far have returned no help either from forums (including here), MS site (no Q-articles), and VBA Help. I'll continue searching though.
Hi, as an attempt to improve database performance, I have split a MS Access 2003 database. I have successfully split the database and saved the backend onto the server. My question is, where is the front end. or do I have to create it?
I have a database that I've created for someone else to use. It's split into a front and back end. The user will be placing the front end on her desktop PC and the back end on a network server.
She also will be taking the database home to use from time to time. My problem is that when the database is split, upon opening, it looks for the back end on the network drive, which is unavailable when she's away from the office.
Is there a way to tell the Access to look in a directory relative to the one it's in?
I have a call tracking database with 5 active users. Ocasionally the database will freeze, usually for several people at once. It will say: "Can not update record; Currently Locked"
The only way to fix it is to close and re-open. I split the database, compiled it and then created an MDE file to distribute. They are using copies of the front-end, not links. The database locking more and more every day. But we are using it more. After parusing the forum I'm starting to suspect that this is a problem of "Primary Key duplication" If everyone trys to create a record at the same time, would the database lock because we all created the same record at the same time?
If so, how do I get around this? Use something other than Autonumber for the primary key? Or is this an entirely different problem?
Hi all, I have noticed that ever since i split my database there is a considerable slow down of load time! When multiple users are on, it is also incredibly slow. is there a practice to follow to speed up the database? each user has their own front end, so im not sure if there is something else that can be done to speed it up
I am new to split database format... If I put the backend on say windows server 2000 or 2003 in a folder, is there anything else I need to do? Any setting on the server?? Or do I need a specific type of server os ie sql server etc?
I have a relatively small database of approx 28 MB - for 5 users max on Access 2007 -since the upgrade from '97 I have noticed a significant degradation in performance over the network - not so much on my machine which is the server/host machine but on the clients. All are Pentium/Celeron processors and recently I have beefed up the working memory to approx. 750MB/ 1GB on all these machines.
Even so, on occasion, I might type something in a field on a form - Access seems to 'fall asleep' for 10 seconds or so and then wake up again. Indeed, the window caption states (Not responding) .... This is not happening all the time but enough that when it does happen it is particulalry frustrating. Has anyone else had a similar experience?
I am thinking of splitting the database into a front / back end to resolve this issue but perhaps it is not a network traffic problem / the database isnt really that big considering others that I have read about on the forum that run into 100 of MBs! - can anyone suggest this a sensible idea / or could I regret at a later date?
