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.
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.
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
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.
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!
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.
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've been developing a new db and have been adding buttons to forms all along without any issue.
I would create a button and under the event tab in the properties sheet all the buttons used to indicate "On Click" would produce an [Event Procedure]. Suddenly the "On Click" now indicates an [Embedded Macro] is going to run, which is not what I really want to have happen......
I have a query screen which worked. It has a header and some details. Now only the header shows up. No detail is visible. I look at the design all these fields are visible, but in reality they are not.
I have a form that I have opening in Filter by Form mode. It WAS working flawlessly, at least it was opening in that mode. It IS still requiring me to click on Toggle Fields once data is entered into controls to filter by, but that's another issue (I wrote a recent comment, but haven't gotten any response). Something different is happening suddenly that wasn't happening before. This form is a copy of a form needed to enter data.
Both forms read from a table which has several required fields. Suddenly, when I open the form to find records in ANY mode it's making me enter something into these required fields, even though I'm not searching/filtering by them. The message comes up "You must enter a value in the [Specific Required Field name here] Field." What did I do to make this start happening? How do I stop it? I DO want something to need to be entered in the required fields when new records are being entered and when things are being changed. However, I don't want it to be required during search processes.
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.
The above image is of a table which I need to update according to a new data on daily basis. As you can see when I added two records at the last , the AutoNumber primary key of the table jumped by thousands . I have used the following query to update the table
Code: db.Execute "INSERT INTO D_Counterparty (CPTY_ENTITY_ID,CPTY_DESC)"_ & "SELECT Ctpy_Entity_Id,Ctpy_Entity_Legal_Nm"_ & "FROM NewCU LEFT JOIN D_Counterparty ON D_Counterparty.CPTY_ENTITY_ID=NewCU.Ctpy_Entity_Id"
I never changed the AutoNumber from incremental to random and I have also tried re-seeding it but had no success. Also when I inserted the sample values using a sample table ,the AutoNumber was working fine . Here's that query
Code: db.Execute "INSERT INTO D_Counterparty (CPTY_ENTITY_ID,CPTY_DESC,) SELECT a,b, FROM sample"
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!!
When I click a tab (table,queries,reports or module) I receive an error that says (" isn't an index in this table. Look in the indexes collection of the TableDef object to determine the valid index names). Please help.
i have been sick for quite a while,But back on track now.In the past i was building a car event db and would like to finish it.I have checked it out and there seems to be a few errors that i can't remember anything about.
you must have outlook installed otherwise some missing references come up.also there seems to be a problem with the date on the invoice form,the backup section in utilites.
If someone could have a look and point me in the right direction it would be greatly appreciated.
I have database which has worked normally, and just made a couple of amendments
I then go to edit a form (which I had not amended) and get an Access has an fatal error etc.
I reopened it. and repaired compiled etc, but absolutely impossible to get into this form. Access crashes every time I try to do something with it. I can't even delete the form.
(This was A97)
There's no problem, I just got my last back up, and imported the changes I had made from the faulty dbs -
I just wondered if anyone else ever got these issues, and what they did about them.
I've created an Access Database off of an old Fox Pro System. What I need to do is take the data from the tables in the old system and convert them in Access '03. I have roughly 4600 records to transfer.
When I copy the data from the old system and paste it in an Access table, only 300 or so records are pasted. Also, when I check the paste errors, there are less than 100 in there. Where are they going?
Some of the files aren't pasting because there were input errors on some. Others are linked with a department and Acct number and some of those are no longer current, so another reason why some of these records aren't pasting. This is a problem, but should only be around 500-1000 records tops.
I have noticed if I paste less at a time, I get less errors and more are actually copied through, but I don't know exactly how many I should do at a time?
Some questions I have are:
1. How many should I paste at a time?
2. Am I missing something with the paste errors, is there like a setting I can adjust?
3. Is there a better way to convert this old table into a new table?
Any suggestions or comments would be great because I have been stuck on this for a while and I DO NOT want to input these records one by one.
Thank you in advance,
Josh
Here's an email I sent to one of my friends seeing if he had any insight. I might explain my problem a little better here:
Purchasing Department has an old Fox Pro Contract System. I made this same system into Access and it works great. My problem is now converting the tables from the old system into the new system. There are approx. 4200 records. I have tried pasting them all in together and also sections at a time, but everything I do so, I get more or less copied through, and more or less paste errors displaying the ones that hadn’t copied over.
The reason some are not pasting in is because of old user input errors. Another reason is department and account numbers have changed therefore when the copy takes place, if Access doesn’t recognize an Acct number, then it cannot relate it to a department and will not paste in. I’m fine with that though. The problem I’m having is I’m always getting different amounts of errors each time I do this. For example, I did the first 500 records. Had 21 paste errors, all the others pasted fine. I then tried to do less so I copied the first 400 and only received 3 errors, but then I did the next 400 after that and only 200 pasted through and it only displayed 20 or so paste errors. I think there are roughly 400-500 bad records so I’m not understanding why all but those 400-500 paste.
I've created an Access Database off of an old Fox Pro System. What I need to do is take the data from the tables in the old system and convert them in Access '03. I have roughly 4600 records to transfer.
When I copy the data from the old system and paste it in an Access table, only 300 or so records are pasted. Also, when I check the paste errors, there are less than 100 in there. Where are they going?
Some of the files aren't pasting because there were input errors on some. Others are linked with a department and Acct number and some of those are no longer current, so another reason why some of these records aren't pasting. This is a problem, but should only be around 500-1000 records tops.
I have noticed if I paste less at a time, I get less errors and more are actually copied through, but I don't know exactly how many I should do at a time?
Some questions I have are:
1. How many should I paste at a time?
2. Am I missing something with the paste errors, is there like a setting I can adjust?
3. Is there a better way to convert this old table into a new table?
Any suggestions or comments would be great because I have been stuck on this for a while and I DO NOT want to input these records one by one.....
I do a query to remove "." from a list of my servers. This works great, but for every name on the list without a "." I get an error in the output. Is there any way to remove these errors from the output, so I only see the data that has been properly pruned down?
I have an unbound combo box that is sporadically failing with an error message when an entry in its pulldown list is selected. The error message is to the effect: 'The value you entered isn't valid for this field' .
The record source for the combo box is a table/query which is updated by an event triggered by another control on the form. That code also sets the Format property of the combo box to match the native Format of the field from which the combo box is retrieving the data. So data from Yes/No field, a date field, or a currency field, for example, display properly in the revised combo box. When the combo box is populated from a source field that has no special format (the usual case, as with text fields), the code resets the combo box's Format to "".
Again, the combo box has no control source (it is unbound). So, the only culprit for an error message like this that I can think of is this Format property. Yet, when the error occurs, the combo box's Format is properly set to "", which should permit any kind of data, and I try entering any kind of data at all -- all data is rejected with this error message.
this is probably an old one but its catching me out. I'm writing a sports club database in ASP. When users submit their club details in the form to Access, I get errors if it has the characters ' in any of the fields. I've managed to get around " by replacing it with "". However, this doesn't seem to work with '
I'm new to ASP... anyhow the part of my form which deals with this is:
I also do a bit more error checking on the email address, for length, @ etc. This bit seems to work ok. However, Any tips on how to improve the error handling for ' or " before its submitted to access is appreciated.
