I have a time reporting database called Productivity. I also have a split version with ProductivityFE containing the forms, queries, and reports and ProductivityTables containing the data. All three are on my PC. Each month I update Productivity with new records and run a report or two to check things out. Then from ProductivityTables I import the data tables. If there are any updates to the forms, queries, and reports these are imported into ProductivityFE. I again test a couple of reports before finally placing both FE and Tables on a server. The managers then place a copy of FE (from the server) onto their desktop and run reports from there. So far so good until this month when I created a new query for a new report. It runs fine in Productivity, but in the split database (on my PC) I get the error 'Invalid Bracketing of name [tblCostcenters.ProdCenter]'.
Below is the SQl from the query. Of note here is a time record contains both a home costcenter and a worked costcenter for the employee. I have two instances of tblCostcenters in order to reference the field ProdCenter for both the home and worked costcenters. The code fails at the first IIF statement on [tblCostcenters.ProdCenter]. Based on other posts on this sight I tried replacing these brackets with [tblCostcenters].[ProdCenter] and [tblCostcenters_1].[ProdCenter] and it seemed to be working until the last bracketing was changed, after which I was faced with the parameter query dialog box looking for a value for tblCostcenters.ProdCenter.
So I'm stumped. Why would the query work in a single database but not in a split database?
SELECT tbleTimeData.HCCtr, tblCostcenters.Title AS HTitle, tblCostcenters.ProdCenter AS HProdCenter, tbleTimeData.WCCtr, tblCostcenters_1.Title AS WTitle, IIf([WCCtr]="","Other Affiliates",IIf([tblCostcenters.ProdCenter]<>[tblCostcenters_1.ProdCenter],"Outside Product Center",IIf(IsNull([tblCostcenters_1.ProdCenter]),"Outside Product Center","Within Product Center"))) AS WProdCenter, Sum(tbleTimeData.Hours) AS SumOfHours
FROM (tbleTimeData LEFT JOIN tblCostcenters ON tbleTimeData.HCCtr = tblCostcenters.Costcenter) LEFT JOIN tblCostcenters AS tblCostcenters_1 ON tbleTimeData.WCCtr = tblCostcenters_1.Costcenter
WHERE (((tbleTimeData.FY)=[Forms]![frmMainMenu]![cboFY]) AND ((tbleTimeData.FP) Between IIf(IsNull([Forms]![frmMainMenu]![cboFPFrom]),[Forms]![frmMainMenu]![cboFPTo],[Forms]![frmMainMenu]![cboFPFrom]) And IIf(IsNull([Forms]![frmMainMenu]![cboFPTo]),[Forms]![frmMainMenu]![cboFPFrom],[Forms]![frmMainMenu]![cboFPTo])))
GROUP BY tbleTimeData.HCCtr, tblCostcenters.Title, tblCostcenters.ProdCenter, tbleTimeData.WCCtr, tblCostcenters_1.Title, IIf([WCCtr]="","Other Affiliates",IIf([tblCostcenters.ProdCenter]<>[tblCostcenters_1.ProdCenter],"Outside Product Center",IIf(IsNull([tblCostcenters_1.ProdCenter]),"Outside Product Center","Within Product Center")))
HAVING (((tbleTimeData.HCCtr) Between IIf(IsNull([Forms]![frmMainMenu]![cboCCtrFrom]),[Forms]![frmMainMenu]![cboCCtrTo],[Forms]![frmMainMenu]![cboCCtrFrom]) And IIf(IsNull([Forms]![frmMainMenu]![cboCCtrTo]),[Forms]![frmMainMenu]![cboCCtrFrom],[Forms]![frmMainMenu]![cboCCtrTo])) AND ((tbleTimeData.WCCtr)<>[HCCtr]));
I am trying to import data into Excel using a New Database Query, but receive the error "Invalid Bracketing of Name 'mdb.'." I can preview the data in the Query wizard, so it seems like Excel is finding the data, but I always get the above error.
I have performed the exact same process on another machine and it works fine. Is it possible that excel or access settings are causing this error, or perhaps my ms office is corrupt?
Any help would be greatly appreciated. Thanks a lot.
I am getting this invalid use of bracketing error Set objMyRecordset = CurrentDb.OpenRecordset("select itemno from " & Chr(34) & "[" & icitem & "]" & Chr(34))
I've developed a database that was working fine until I split it to use in a network enviroment. The problem is a make-table query that now make it's table in the front end instead of the back-end. I need to run a make-table query because the query uses a custom function which then causes errors when the query is accessed by a web form that I use.
The only way I thought of getting round it was to create a permanent table in the back-end which is cleared every time and an append query used to populate it.
i have developed an application in access 2010 . and split into front and back end . now i want to add more tables in back end and i need to define lookup list in table definition from the query presently in front end . when i get into lookup list and query builder doesnt show front end content ... how to solve this problem ?
I have a split database and need a field (Combo type) in the table to lookup values from a query in the front end. How do I do this as it doesn't see the querys because the front and back end are split?
We have an Access 2010 database that is accessed by some users from another location. Each user has their own copy of the front end. For some reason two users in our Sydney office enter orders, but after they have entered and saved the order, sometimes for no apparent reason they get an "invalid argument" error message and all the data in the order has been converted to hieroglyphics. I cannot seem replicate this from my server location.
It seems to only occur from our Sydney based server. Could it be that each user's copy of the front end is located on the same virtual drive on our Melbourne based server? Should I move the Sydney user's copies of the front end to the Sydney based server?I think it might be the growing size of the database but I compacting doesn't reduce it by much.
: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 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?
Hi All, I have a split database. One of the processes I've created, copies a new table from a previously created blank table. It then imports data from an Excel spreadsheet into the newly created table. My problem is that now when the import occurs, the data is getting imported into both the new table as well as the blank table. For some reason, this only occcurs after the database is split. I've tested on a backup copy that is not split and everything works fine.
I have this problem. I have successfully split a database into a front end and a back end database. Well it has been going great for about 2 weeks now but the thing is I would like to take the database home over the weekend to work on it. I don't know how to properly put a split database on a CD. Every time I tried copying it, I get an error when I get home and try to use the CD. Can someone point me on the right path.
Also one more thing, is it possible to have a password on the backend database to protect the information from snoops?
