What would cause Access to suddenly close without warning while busy with a query?
No error messages, nothing! The query is a fairly big one that normally takes about 6 minutes to run, but has had no problem with it for a number of years. A new drive used for back-up purposes was recently fitted to my PC which now has 3 internal hard drives.
Could this problem be caused by a bad memory handling configuration? The original setup that worked before may have been changed when the new drive was installed. The XP Page File size for example may have been changed.
My acccess (.mde) application suddenly slowed down. I have increased the size for some fields in some Tables. Is it could be the reason for this? Is there any way i can get the speed back.
Recently Access has started to suddenly close. Usually when I have been developing although I do not appreas to have lost anything as I Save, Save, Save all the time. Last week I had a report that a live access 2000 is doing the same thing. Users are in the middle of entering data and suddenly the database is gone, with no messages. They can re-open the database and continue.
Anyone else experiencing this problem with Access 2000?
It was working firn till yesterday morning. I have not made any changes in this. But now i am encountring the following error
Run time error 3125 The database engine can't find ". Make sure it is a valid parameter or alias name, that it doesn't include invalid characters or punctuation, and that the name isn't too long.
Please help me. Same thing working properly in other application . Same code same database.
I run several databases daily - after running two of them (at different times), the database itself closes but the Access program stays open. In order to close that program, I have to close it out using the Task Manager.
Any suggested solutions? Thanks (as always) for your assistance.
I have an access2000 db. Many tables, forms, reps ect... at random times it will just close. Don't know why. No errors, no reason why. It just closes. Is this common and is there any fix?
I was trying to access this particular MS-ACCESS file which serves as a DB for a software. But the file opens and closes in a split of a second and was impossible to view its structure. :mad: I beleive it's made to respond so by the programmers in order to hide the content. Can anyone please help me open this file? PLEASE...
I have an application that when in design master shuts down when I attempt to open a certain form. I have traced the problem to a linked field from another table, by creating a new form and ommitting the said field, problem is its a required field!
If I copy the database (Backup) and run it as a replica it does not happen, if I then convert the replica to design master it happens.
This application has worked fine in the past, but now I find it stops cold saying a particular linked table is read-only. I've looked around and all I can find in the various forums is how to MAKE a table read-only. Reversing that process seems very difficult.
The application is a copy of another that now exhibits the same problem. Each uses a different data mdb - part of the development I'm doing involves changing a different table. I'm developing changes to the application in this separate copy.
I can't tell if other tables would have this problem - the table in question is the very first used (initialization routine) and I can't get past it without deactivating a bunch of code.
I am having a problem running Access 2007 runtime on a workstation. I have set up the 2007 database (.accdb) on our server and am able to connect to it and open it from the pc that has Access 2007 full version installed and it works fine.
I also installed Access 2007 runtime on another PC and was able to open the database using the runtime version just fine.
However, on this other PC, I installed the runtime version, and when I use the command line (msaccess.exe /runtime \serverdirectorydatabase.accdb) to open the database in runtime mode, Access opens for a split second and then closes immediately.
When I just run msaccess.exe, it opens the runtime version and says that I have not specified a database, as expected. So, I am wondering why it is not opening the database when i DO specifiy the database.
If i specify an incorrect directory for the database, it opens the runtime version and a dialog appears telling me that a database was not found, and upon clicking OK, the program closes.
I can say, that when I run it off the computer that works through the runtime version, I get a security warning telling me that there are potentially unsafe elements in the database, but i just have to click OPEN and it still opens it fine.
Perhaps the non-working PC is denying it access due to these security issues?
I can't seem to figure this out, and any help is appreciated.
Access database 2007: I have a database with some forms init but when i type my username and password to open the main menu to insert data the form shows 1 second and closes the whole database. I don't know whether the problem is the VB code or the microsoft.
I hit ok and the usual invoice_id param text box message box appears again.
Once that is over, I gain access. I can browse to the form - frm_system, open the sub-form sub_frm_invoices and remove the invoice_id field. Once I re-add it everything works fine (until I close the application).
I initially thought it was because the database was set to "compact on close" but I disabled that and it is still occuring .
I know this is the cause but as the sub-form itself uses a table record-source I know the field exists - not to mention I can simply delete and re-add it to fix it temporarily.
This behavior occurs when a field, a criteria, an expression, or a control in a query, a form, or a report references a name that Access cannot find. For example, a name could be misspelled or a field may not be available within that scope.
Basically it looks like the textbox displaying the invoice_id on the form is the problem. I can't figure out why though. When I remove it everything works - the queries work if I recreate it as well..
Hello, I have an Access database that for some reason just converted to "read-only". I used to be able to open the database and do whatever, now it says it is read only. I have checked the permissions for both the database itself and the folder it is in and they both do not have "read-only" selected. What I really don't understand is if I use my application that uses the database (written in ColdFusion) I get the error - must use an updateable query. BUT if I continue to hit refresh, then it'll work! So it's like it works sometimes, but not all the time - as if it's switching back and forth between read-only and not read-only. Does anyone have any suggestions? Thank you!!
We have an access db that has been working fine for ages and now when we click on a New Record button we are getting the following error:-
Run time error 2105 - you can't go to the specified record. erroring out on the line DoCmd.GoToRecord , , acNewRec. We are not aware of anything changing on the PC that the db is sitting on. I have spent the whole day searching the web but have found nothing helpful.
I have compacted and repaired the db, even went to the form/table security to see if all users can edd/add.
I have a database running for the last 6 or so years (A97) and have the ctl-shift disable enable code in it to stop people tinkering about with it.
The database was aparently working fine yesterday and today it's decided to be read-only so no-one can update the data.
It's on a server - all permissions ok and not read-only.
I can't get the disable/enable code to work either. So basically, it's locked for any development changes and it's locked for any data changes.
The IT boys are going to take a backup from the tapes of the server and re-install it, so it should be ok, but I've never had this happen before and the database is used daily for the last 6 years with no problems.
Any speculative thoughts?
[edit] I have done a search and couldn't find anything that fitted the situation
this never used to be an issue, but all of the sudden it just started happening.
Setup: frmCustomers (data: tblCustomers) is linked to sfrmJobs (data: tblJobs) via CustomerID (autonumber). Depending on their [Status] in frmCustomers (dropdown, either "Customer", "Lead", "Lead-to-customer" or null), a customer may or may not have a job in tblJobs (or may have more than one).
Issue: When scrolling through my list of customers , after passing by a "Lead" (or if i just select a "Lead" to begin with), who cannot and does not have a job, the subform does not show any jobs from that point on for people who do have jobs. Also when I create a new job and then attempt to insert data, it tells me that I have an invalid use of null, which is weird because the only field that needs to exist is the customerID, and that's created automatically.
Diagnosis: I think it has something to do with the CustomerID not functioning correctly, which i don't understand at all, or somehow not getting passed to the subform. i've entered plenty of new customers into the program without an issue, and i used to be able to scroll through all of them and have all of them show up all the time. Additionally, even after i clicked away all the "index or primary key cannot contain a null value" errors, it still gave me a CustomerID, but after I created a job (again, "index or pk blah blah") for a customer, i looked at the table and it showed that the JobID (primary key of tblJobs, is not autonumber) was recorded, but not the customerID.
Cry For Help: Please help me! I discovered this bug almost 5 minutes after publicly deploying my program to my client's company, and if he finds it before i can fix it, i'm toast. please please help!
An Access database table I'm looking at has a date column, where date is entered in UK format (dd/mm/yyyy). However, upon entering the database, the date is somehow converted into US format, despite me passing the date into the table as dd/mm/yyyy.
The trouble started when someone else worked on the database - leaving us now with all of the old records in UK format (correct) but all new entries to that column in US format.
Please note, when I open the Access table, all of the dates for the past 2 years or so are fine (dd/mm/yyyy) but recently, since someone else worked on the file, the new records are appearing as mm/dd/yyyy. Within the same table column we're getting apparently mixed formats.
I'm aware of using session.lcid=2057, but would prefer just to be able to have the dates appear in the right format in the database itself rather than having to use this (I'm concerned if I use lcid, it might balls up the older, correct records in the table).
How can this have suddenly changed, and more importantly, how can I get the records into the table in UK format?
I have a form that worked when I left work Tuesday. It is supposed to look at all the information in my "courses" table in descending order by year, ascending order by date, in edit mode. There is also a look-up list that allows me to select the date of the course and jump to that record.
I came in today and it doesn't work! The form LOOKS like it's in add mode--completely empty. the data is still in the table. I checked all the properties and they all look right. The query still looks like it did when I left. It just quit! When I use the look-up list the dates appear in the list, but nothing happens when I select it.
I know I'm not giving you much to go on, but any ideas?
I have written a very simple query which get's it's criteria from a form I also created, which couldn't be any simpler itself. The form simply has a text box that I enter a value into, in this case, the date in a specific format "20041019". The query then pulls all records according to the form value. This query has always worked fine for weeks now. Today, suddenly it would not return any records. If I go into the SQL and manually enter "20041019" it will pull the appropriate records. It will NOT function when relying on the form value though. This has happened to me in the past, of course I did not document what I did to overcome the obstacle though. I have tried matchign the formats of the field in the table to the text box in the form so that they are both general numbers with 0 decimal places, originally they were both text format and it worked. I can't seem to figure out why this would happen. If anyone has any suggestions, I would GREATLY appreciate it.
I created a form with an "exit" button and a "return to main menu" button on the form. but when I am on the last data and press tab the form closes automatically. what could be the reason. Do I have to put some condition on the macro I have created for the two buttons listed above. I have just put "action" without any conditions on both the two buttons.
I have a form that records when a user edits a record. This change is only recorded when the user clicks the "update record/save" command button. What I need help with is capturing the changes made when a user edits the record in any field and doesn't click the save button upon closing the form. If the user doesn't edit any fields in the record, a new instance of this edit will not be saved to my edited records table and the form just closes
I created an MDE file for my application it's a split db when I hit the exit command button on the MDB version it quits the application correctly but when I do the same thing on the MDE version, it leaves the database window open on the taskbar.
