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've started getting this vague and in no way helpful message every time I attempt to look at any of the VBA behind my forms, modules, etc.
Luckily, the front end is stored separately from the data, but it's still preventing me from making changes to the forms.
I assume it means corruption of some kind has occurred, but I'm unclear as to what has caused it. Clicking on 'Debug' does nothing. Immediately below the above message it asks if I want to compact and repair the database. I say 'yes' and this also achieves nothing.
In addition, I have tried the following to fix it:
1) Opening the database window and go to Compact and Repair, via the Tools menu. This appears to fix the problem, in that I can then view the VBA code. However, the next time I log out and back into the db, I get the same problem all over again. 2) I am currently importing all of the items (forms, tables, menus, macros - the lot) from the problematic databasse into a blank one, in the hope that this will fix things. This is either taking an extremely long time or the process is hanging. Does anyone know how long this typically takes and what 'Task Manager' should say is happening? The db is 42.5Mb, if that makes a difference.
The above are the only suggestions I've been able to find.
1) Is there anything else that I can try to fix this?
2) What has happened to start causing this problem? I've run through suggested things like suddenly closing the db incorrectly, opening it using another application, etc. and none of these apply.
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?
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 seem to be having problems with Access and a certain query today. The query has always run OK, however I have linked a field in the query to a textbox on a form (Ive done this well before with other queries). For some reason, everytime i try to run the query now, I get the general "MS Access has encountered a problem. Please report this to MS". Does anyone know if this is a known glitch in Access, or if there is a way around it?
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'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.
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"
I have a database on a network which has no security setup; everyone who has rights to its directory has full rights to the application. From time to time, it becomes "Read Only" and no one can do anything that requires writing to the local tables (the back end database is "Read Only" for everyone.) Checking the database properties shows the database as not being "Read Only" and changing it to read only and back again does nothing.
So far, the only way I have been able to solve this problem is to replace the "Read Only" database with a backup copy that is not "Read Only".
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables Dim db As DAO.Database Dim qdf As DAO.QueryDef Dim varItem As Variant Dim strCriteria As String Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM qryContractListSummarybyDateContract3TYPEBREAK WHERE qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri Masonry NSW');'
I'm from Vietnam and my English is bad. In my database, I have only a table named tblEmployees, which contains these following fields: Employee_ID (data type: text), Name (text), Salary (number) and Allowance (number). I build a form bound to this table. In the footer of this form, I have a textbox control named txtSumSalary that contains the expression: =Sum([Salary]). Everythings is OK. But when I build an another textbox named txtSumAllowance that contains the expression: =Sum([Allowancess]) (I misspelled this field intentionally), the result are error #error in both textbox controls. I don't understand why the textbox txtSumAllowance wrong, the textbox txtSumSalary is wrong too. Help me!!! Thanks a lot!
One of my user gets the following error from MS Access running from his local machine and linking to the database & appropriate tables. The front end MS Access application uses back end SQL server to get info from. ODBC connections are in place, folder/file NTFS security for this user is also in place. he is admin on his PC. His machine uses DHCP to connect to the network. One thing I'd like to mention is: We have Citrix server on which this application is published and this user can connect and perform the same tasks using the Citrix client. He is having errors in connecting to the tables Only when he launches locally.
Recently he got new upgraded PC and since than this problem arose. He was OK on his older PC. Any ideas what & where else to look?
In my opinion, it must be some tweak that needs to be done on user's machine.
PS: The problem appeared only on this user's new PC, from his old PC he was able to get to the tables and all other good stuff. All other users in the same group do not have any problems at all.
