Hi all, 1st post. I'm and Access n00b I'm afraid, so take it easy. I normally use php/mysql, but have been roped in to fixing a broken access database.
I've got an Access database, and a fileserver is holding the data (mdb file), but I've got around 10 machines which access the database thru a frontend (mdb file).
Now, this has been working fine until today, where I am trying to view one table (Orders), and access bombs out. It shuts down instantly with no warnings. It does this on every machine, so I think it is a database problem. I can view the data if I open the standalone data file, but I cannot view the data thru the frontend.
I need to fix this asap... what's causing the crash? I didn't make the front end, but if I could look at the code, I may be able to see where it's failing.
My MS 2000 Access application is crashing and returns a msg something like this: "Your Access application caused an error and Access must be closed" This occurs only when I execute some forms; always the same forms cause the problem. Somebody told me to copy the .mdb to another place in my HD and change the names of the forms. I did it and it always works well! Any good reason for that? My app is not yet splited in FE and BE. Splitting would help?
Wondering if anyone had tried this yet, and if so, encountered any problems. I have a few existing DB's in the office. Split with backend on server in mdb format. I am now using both 2003 and 2007... BUT.. Now that the runtime is out I would like to make my future updates in 2007. So the question is... Has anyone used a 2007 file format frontend with a 2000 to 2003 file format backend? I understand that the new field properties wouldn't be available in the mdb backend, but besides that, would they still link properly?Thanks
I don't know if this is caused by Access (2003) itself, or somethign else, such as the JET drivers. Whenever I load up anything in Access it crashes saying I can repair it and restart access... no matter what I load.
Also, it seems other programs that connect to a database only retrieve 'nothing' from the tables and queries. I'm quite confused, any help would be wonderful right now.
on a small scale this code works, but when my inventory table has all of the 2000 records it crashes, any ideas. I can ftp my database if needed
Code: Dim ColorDim StartPointDim RsItem As DAO.RecordsetDim RsNewItem As DAO.Recordset 'Grab the inventorySet RsItem = CurrentDb.OpenRecordset("select ItemId,Description1,description2,quantityonhand from item")'grab the table that will have the new item and description addedSet RsNewItem = CurrentDb.OpenRecordset("select * from newitems") With RsItem While Not .EOF StartPoint = 1Start:'find out if the last numbers is numeric or notIf IsNumeric(Mid(Right(.Fields!itemid, StartPoint), 1, 1)) = True Then'see if the start point is the last letter or notIf StartPoint = 1 Then 'meaning there is no colour indicated at the end of item Else'add the quantity and the color to the newItem tableColor = Right(.Fields!itemid, StartPoint - 1)RsNewItem.AddNewRsNewItem!Description = .Fields!quantityOnHand & ColorRsNewItem!itemid = .Fields!itemidRsNewItem.UpdateEnd If Else'move the startpoint to the next letter in itemStartPoint = StartPoint + 1GoTo StartEnd If .MoveNextWendEnd With
Every time I try to import a CSV file into my Access database it crashes. I've tried repairing it but the repaired database crashes as well. Any ideas on what could cause this?
Hi. I have been fixing up some access 97 programs on the computer systems at my work. The main changes I made was creating a search function using a query behind a form to search the database (no more than only 90,000 records). I am running a novell server. The data tables are in a database on the server. The access program on the desktops have their own access database program that use linked tables to the data tables on the server. The following is my issue:
Apparently, some of the changes I made to the searches caused the server buffer to become full and not flush itself. Anytime I was working on creating the fixes, it seemed to make the server crash. I 'm just wondering if anyone has had a similar problem with access 97 running on a novell server and causing any buffer issues. Any ideas on how to prevent the server from crashing?
I have a database that currently has security in place so that users input their own usernames and passwords to access the database. The users have recently been added to a windows 2000 server and I want to be able to use their windows 2000 server logon credentials to provide them with automatic access to the database. Is there anyone out there who knows how to set this up? It is a rather urgent request if you could get back to me either on this forum or via email
I am opening and closing a series of Excel 2000 Workbooks using Access 2000 VBA and want this sequence to be able to complete without any human intervention.
However, there are 2 instances when this stops and waits for a human option to be selected:
1. When the spreadsheet is password protected 2. When the spreadsheet has automatic links I get the message:
"The Workbook you opened contains automatic links to information in another workbook. Do you want to update this workbook with changes made to the other workbook?"
How can I code it so that in situation 1 it skips this file and in situation 2 it automatically defaults to do not update?
If I have a report in MS Access 2000 generated based on the criteria selected of a project with work order "9999" with the labor costs, materials costs and the Totals of each crew1, crew2,... and I would like to have those expenditures populated in corresponding cel in Excel for each crew, HOW would I do it?
To think it out loud, could I create a button on a form, so when I select the criteria for the work order, and when I click the button, it should refresh/update the Exel file with the new data...?? How do I write VBA code for that...?
I am trying to build an event when I double click a field. As soon as I click on Code Builder, access crashes. It does this with every access database I open.
I have recently been doing a conversion for my boss for a access 2000 database (both front and backend) to a MSSQL backend.
I finished the conversion today (as quite a lot of the code / queries ran slow due to access running the queries locally rather than on the server). And tested it on my and my boss's machine with no problems so he gave the go ahead to update everybody to our new mssql 2000 backend with the modified frontend.
This is when the problems started; We had two different sets of forms for accessing one of our databases systems - the log system, one is the original dynaset based form, and the other is a newer set which uses snapshot views and preforms updates via queries. Nobody uses the old dyanset system apart from my boss and one of the administrative team as they have things on that window which they need to see. About 30 minutes into the release of the new database the system frooze up on my bosses computer and nobody could create a new log (the server was timing out). I assumed this had something to do with the old dynaset's creating locks on the table.
I offlined the database and kicked everybody out of the front end, turned it on again and tied again, this time banning everybody from the dynaset system. Within 10 minutes another computer frooze up, again with a timeout on the insert query. I discovered that after you had added a new log to the database it would timeout on all subquent additions (something it hadn't done during testing) . Further investigatiion showed it was the snapshot list window causing the error, so coded the add log window to close the list before preforming the insert query and then reopen it afterwards. This allowed my machine to make multible additions without flaw. So I released a new client to everybody. 15 minutes later it was timing out again, but this time there you could not even make one new record.
I checked for locks on the table though the server management table and couldn't find any for the Log table. I have restarted the SQL server box and with no avil. So I reverted our backend to the access mdb file and told people to use the old client.
I am at a complete lose to why this is happening, if anybody has had any expericences like this or knows the cause please tell me.
Some information on the database in question.
It was made as an access 2 database all intergrated into one file, then it was seperated into two files (frontend and backend). Upgraded to Access 97, then to 2000 before this final update to MSSQL 2000.
The log system has two main tables. The first is the log title / info table which links (one to many) to a log entry table. This problem only occurs on the main log table and does not appear to be reoccurring anywhere else within the database. The main log table has just under 18,000 rows in it.
I have been building an access database at work which would be useful to share with eveyone else at over the network or live server.
Is there a front end I can get for it, or is using the access file itself the only alternative. All i know is html, css and actionscript - so I don't think I can use this. It would have to be pretty basic - I have no idea what kind of technologies are available for me in this regard.
Any suggestions or methods would be very much appreciated!
I am evaluating a program for the use of a customer. It's a VB frontend attached to an Access database.
The backend has no relationships. No table in the backend even has a primary key.
My question: Is this scenario acceptable in any way?
I tend to think not, but am unsure whether the design of the frontend application establishes relationships "on the fly". Even if so, the fact that there are no primary keys makes me think I should dismiss this application out of hand.
I am very good at excel and can program macros. I am being asked to build something in access for my company, or at least manage a build. So here is my question... If we build it without both a front and back end, is it easier to take what you have and switch it to a front and back end? Also, when and why is it better?
I have a simple calculated field (As "Ratio") that is readable in Access 2010 query, but crashes in Excel upon importing/running the query in an .xlsx table.
ERROR MESSAGE in EXCEL: "The query did not run, or the database table could not be opened...check database server..contact your database administrator.."
I am simply taking the cost amounts of each project record (shown as "Record Cost") and dividing it by the "Total Cost" of that project to render "Ratio".
The Total Cost is retrieved from another table.
Testing scenarios: If we exclude Ratio, the whole query import just fine. If we filter the query to one project (i.e. "Project A") the ratio field imports fine.
However, the whole unfiltered query does not with the ratio!
Other testing scenarios:
If we use a constant for the denominator AS "1" in Ratio (i.e. recordcost/1) the whole unfiltered query and ratio field imports fine.
If we use a constant for the numerator AS "1" in Ratio (i.e. 1/totalcost) the whole unfiltered query upon import crashes in Excel.
This is a mock example of the dataset, the actual query has 50K+ records:
Project Service Date Record Cost Total Cost Ratio A Welding 1/1/2012 $100 $120 83% A Plumbing 2/1/2012 $20 $120 17% B Welding 1/1/2012 $50 $75 67% B Plumbing 2/1/2012 $25 $75 33% C Welding 1/1/2012 $40 $61 66% C Plumbing 2/1/2012 $21 $61 34%
If I want to distribute a front end to connect with a MySQL back end ... do I need to set up the system DSN on each workstation that will be using the front end?
If I have an MS Access frontend that connects to an MS Access backend, is there a way to hide/permission block the pathway to the backend's folder but still allow access via the frontend db?
Right now I can't dedicate a server to a more "secure" form of DB or anything like that so I'm stuck with MS Access for now. I just don't want someone looking at, say, a link table path and then navigating to that folder and getting access to backend information.
I'd like to secure my frontend by disabling access to the linked tables, queries etc. I thought converting to .accde would do this but apparently not. Is there a way that this can be achieved?
I am aware that I can disbale the ribbons etc but they can all be turned back on using the options menu.
I have two database applications and they are: - the (A) application is for administration use. - the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks. Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset Dim ObjXLApp As New Excel.Application Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer Dim TotalBlank As Integer, R As Integer, C As Integer Dim BadSheet As Boolean, ImpFail As Boolean Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then MsgBox ("You must select a Program to load.") ObjXLApp.Quit 'Exit from MS Excel Exit Function End If
I've created a database in access 2003 with the default file format being Access 2000. Everything works fine on my computer and many others, all of whom are running different versions of access (2000, 2002 & 2003).
I have not had any problems with this database until recently and in the last few weeks we have had 2 users, both of them being Access 2000 users who have had the same problem.
The problem they are having is that when they click on any of the switchboard items, the buttons depress an then come back up again when the cursor is moved away, but nothing else happens - no action, no error message - nothing!!! Its the same for all of the buttons on the switchboard.
Does anyone know what is causing this? I have another computer with Access 2000 on it and this works fine, as it does on several other computers runiing Access 2000, I just cannot understand why it is not working on these 2 particular machine.......
I have recently installed access 2003 w/access 97 installed both are on my hard drive. When I create a new db in access 2003 it saves it in an access 2000 format. Does any one know why it does this?
