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 subform which users log their daily working hours (Mon - Fri) for 2 weeks. The subform is limiting the number of records to 10 or less. I would like to begin including the weekend in the form but don't want to include them as part of the 10.
Here is my code which works fine if I am only looking at the recordcount values.
The date field is [Reporting Date]
Private Sub Form_Current() If RecordsetClone.RecordCount >= 10 Then Me.AllowAdditions = False Else If RecordsetClone.RecordCount <= 10 Then Me.AllowAdditions = True End If End If End Sub
I have a database (split into front and backend). Users populate the table using a form on the front end. Recently, it has been pointed out that some of the data entered into one specific textbox is being changed on the table. The data entered is always has a minimum of a letter and number value i.e. "A1", "A2" etc. Upon examining the table, this has changed into numeric values i.e. "1291", "1061", "852"... etc. Looks like it is translating them into both 3 and 4 digit numerical values by the looks of things. Where more complex data is entered such as "2(A1, A2)" these seem unaffected.
The field is set to text, I have set no validation rule, format or input mask. Just can't see why access is changing these values. It seems to be translating them, but I can't see a pattern.
My problem is, I'm using a form to build up a query using VBA / SQL, and part of the WHERE portion of my SQL statement includes start / end dates. If I then enter dates in the UK format (dd/mm/yyyy), access will, on saving the query, reverse dd and mm if both are 12 or below. I've managed a work-around using Format(strDate, "mm/dd/yyyy") on the strings that store the dates in VBA to convert them to US (mm/dd/yyyy) format before compiling the SQL statement, but I would like to avoid using US dates completely if possible.
my PC regional settings are UK, I have UK dictionary selected within access, what I'm interested to find out is wether there is any way to force access to only use UK format dates, or is this an inherent problem?
im using asp with ms access. code is working fine with normal settings i.e US('mm/dd/yyyy') date format
my task is - select records from a table(CPST) between two dates which the user must enter dates in the format UK('dd/mm/yy'). user will enter dates FromDate and ToDate in Form1.asp. then i carry those two fields with request.form and store in two strings as strFromDate and strToDate.
then i used query to get the records in the second page- strQueryString="SELECT * FROM CPST where dt >= #" & strFromDate & "# AND dt <= #" & strToDate & "#"
so first i want to enter date in UK('dd/mm/yy') format and those entered dates should compare with table dates which are in US Format then i want to get records for the specified period and display the date in UK again in report. since ms access takes date in the US format('mm/dd/yyyy') normally. im able to give date in UK format but not able either to get records or display in UK format. i think u can understand my problem and give the solution. if u dont understand i will explain again.
problem is user must enter in 'dd/mm/yy' format only not even in 'dd/mm/yyyy'.
Hi, I am a longtime Excel user, and am now migrating some work to Access.
I have 2 fields dealing with dates in the format mm/dd/yyyy hh:mm, OPEN and CLOSE
I'd like to get the difference between the two in hours, but I have no idea how or where to do this in Access. I'm assuming it is put into the queries, but it would be easier if I could just put it in the table.
Here is an example 1/1/2008 1:00 1/2/2008 2:00 I want the result to be "25"
I upgraded to Access-2010 and the Text File Import function will not recognize dates in the format YYYY-MM-DD. The import dialogue sees enough to recognize the field as a date, but then every date encountered is written to the Import-Errors table. This is true whether the file has a .txt or .csv extension. The actual file format is .csv.
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.
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.
I am fairly new to access but so far I have been able to get what i need from it, until now. I am trying to find a way of comparing two sets of data to find out an employee's average productivty.
Table 1 -Hours Worked (by day) - contains 'name' 'date' and '# of hours' worked - an employee would enter the hours here on a daily basis
Table 2 - Contracts Keyed (by month) - contains the number of contracts worked that is derived from seperate system - this is entered on a monthly basis (so for example: John keyed 30 contracts for the month of January) - the system i am pulling this info from does not have the ability to pull a daily count of contract per employee, only a range of dates and it then provides the sum for that range (unless I ran a query for each day, for each employee which would take me hours) - employees dont have access to this system to enter their own # of contracts keyed on a daily basis. - for entry, so far i have just been putting the first of the month and then the # of contracts.
In a nutshell, this is the calculation I am trying to create:
(Sum of "# of hours" for the month) / (total "# of contracts keyed" for the month) = employees average hourly productivity.
I have tried to do this with various types of queries and reports but with no luck, I get a prompt saying that access can't compare the 2 fields.
Is there a way to compare the data that is entered daily with the data i would enter monthly?
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"
