hey again, i usually don't post this much and prefer to work it out alone but i have no idea why this isnt working (and the error im getting)
below are screen shots, i am trying to make an improved booking system, but i don't know why its saying i have a null value (i went through and made sure all fields are filled, in all related tables just to make sure)
Hi, To make a long and tedious story short: Does anyone know why Access (2003) creates an index called PrimaryKey and an index called User_ID when I'm in the table design view and ask it to make the User_ID field the primary key?
After years of database development I've only just noticed this. Not normally not a problem but for this: Use ADOX to find the field name of the primay key for a table. I took the code right out of a Access 2000 developers handbook. It creates a collection of the table indexes and steps through them one at a time checking if the PrimaryKey property is true. It hits the index called PrimaryKey and says 'yes it's true, this is the PK', I then go on to use the index.name property in an SQL Select to create an ADO recordset. The only thing is that the index called PrimaryKey is not a field name and the field name User_ID is not a PK :eek: I go into the indexes list in table design and delete and re-create the indexes and PKs as I want and the code works fine.
So, again, why does Access do this? I'm so confused! :confused:
I am trying to figure out how to make my database check to see if the primary key value is a duplicate of anything ive entered previously and if yes, for my database to bring up that record instead of adding a new record.
I know how to do bring up records using a separate combobox (find) but I cant seem to do it using the primary key field itself.
I have 33,099 records in a query, that i'm importing into a table. (don't bother witht he semantics, it's from a linked dbf file) The table does not have a primary key. Given Three Fields (out of 74):
Item_ID Title AltTitle
With the table populated with all the records, I highlighted those three fields in Design View of the table, and told told access to make all three of them the Primary key. Upon attempting to save the table, I got an error message saying that data in the table violated the primary key unique fields rule or what not. So I wanted to make a query to determine where the error occurred. I could not off the top of my head figure out how to select only the duplicated records in a table, so instead, i figured if they violated the Primary Key unique field rule, there should be duplicate entries. so I did this:
select distinctrow item_id, title, alttitle from tbl_Table;
I got 33, 099 records returned on the DISTINCTROW. Strange as that was, I deleted all the records from the table, set the primary key as I wanted it, and then repopulated the table via my sql insert into commands. This time the table reports only 33,093 records, meaning 6 records somehow violate the primary key unique index, but don't violate a DISTINCTROW call. How can i find them to determine how they are violating the primary key unique index? thanks Jaeden "Sifo Dyas" al'Raec Ruiner
In essence its just a save record button which has a macro attached to it to run on mouse down. This macro runs a query to update a table which then updates the form upon saving. The warning messages to say it is deleting the old table and updating with new values keeps popping up even though im using the above code. Any idea on how to supress these warning dialogues when i click save?
Im in a bit of a predicament, I have a main form with 3 subforms named:
Debit/Cred income for day subform Cheque income for day subform PDC income for day subform
and in each of these subforms, I have a field/text box (From a query) which is called "SumOfTotal Cost"
and also in the mainform I have another field/text box called "text73"
Now, all I wanted to simply do was to add all of those fields mentioned together to display them on the main form in another text box as a total so I tried to use this expression in the control source:
=Me!Text73+Me![Debit/Cred income for day subform].Form![SumOfTotal Cost]+Me![Cheque income for day subform].Form![SumOfTotal Cost]+Me![PDC income for day subform].Form![SumOfTotal Cost]
But when i open the form, the text box just appears saying
"#Name?"
I then tried to put brackets at the ends of the code, but still nothing would work, I then tried to access each individual "SumOfTotal Cost" by putting the following in a text box:
=Forms![Cheque Income For Day subform]![SumOfTotal Cost]
but it still comes up with "#Name?".
I am pretty annoyed and I would really appreciate it if someone could please help me
i have a form porblem. I have a search form embedded onto my main form its really a listbox that when i click the records in it they display the record.
prob;em is that when i delete the record it still shows in the listbox
It might be an easy one but I just wasted the past hour deciphering through my code in order to solve the run-time error '94' that I'm getting when trying to execute the following code:
Code: Private Sub cmdUpdateDates_Click() '################################### 'This sub aims at combining the timesheet date and the start and end time into the fields [Start Time] and [End Time]. '################################### Dim intCounter As Integer intCounter = 0 Dim rs As ADODB.Recordset
A bit of a weird one, I've got a query and the criteria for showing records is that one particular field is null. However the query is showing records with the values in the field chosen for the Is Null.
Not sure why this is happening, has anyone come across this problem before?
I am having problems with setting up a set of combo boxes.
What I am trying to do is if combo Productline is empty then in combo PartNumber would show all products but if combo Productline has a value selected then in the combo partnumber would only be able to select the partnumbers in that productline.
Hi, I have some problem with assigmnet with date and string variable. what i wana do is get data from Forms textboxes into variable and then by insert query send to history table.
the problem occurs when there is blank textbox its says invalid use of null.
I have a query where data is first sorted by user input; first field's criteria: [fieldname], then by another field's criteria: Is Null.
I know there are records containing null values in the second field, as I have run a select query with the criteria: Like "*", to make sure they are null, and not zero-length-strings.
I have created a data base over the last few months I just kept adding information in the fields that I created but now have a problem I have the sections in a drop down menus of which access will let me ad info but when I com to save I get this message "Index or primary key cannot contain a null value"
Access will not let me save any added info in any field I have tried all the ways that I know to get round this problem to no avail it is most properly some think silly but I am desperate now as I have worked hard on this project.
I am using Access to connect to a sybase (symposium) database... I pull records depending on what state the record was pegged.... This is based apon a user inpuyting a code on a telephone. Of the user puts a number that does not reprsent any of our set codes it will show the code feild as blank or null. I need to make this blank feild something representable as furhter down my querys it removes these blanks or nulls. I would like the blank field to be shown as "Bad Code"
Any help would be great...
p.s I have used iif and as and like and nothing is working..
I would like to know if is any way to inverse the following code: This: if isnull (txt1) then 'recognise if the box is empty to something like this: if isNotNull (txt1) then 'recognise if the box is not empty
In response to: http://www.access-programmers.co.uk/forums/showthread.php?t=131593
I personally believe 'NULL' should be banned as a possibility entirely. :eek: It has been pounded into my head that 'NULL' is not the same as 'EMPTY' or 'ZERO'; and that it literally means 'NOT KNOWN'. Now consider a contact database that has a field for lets say Apt# or Street Direction such as N or S or ?? as an example. There are many, many instances where these fields would be left blank or empy: NULL | NOT KNOWN. When in fact the situation is known: the object has no such attribute; and in query or some other form of program logic the venerable NZ(subject, response) function may be used which would replace the NULL with a value. Or program logic and or error trapping would be used to handle such occasions. Which is an absurd waste of time and talent IMHO.
Therefore, if there is no applicable attribute to enter (something known) why not say so with 'N/A'? Else what we are saying by using 'NULL' is that we are building a dataset containing data that cannot be known. Kind of like saying
In response to: http://www.access-programmers.co.uk/forums/showthread.php?t=131593
I personally believe 'NULL' should be banned as a possibility entirely. :eek: It has been pounded into my head that 'NULL' is not the same as 'EMPTY' or 'ZERO'; and that it literally means 'NOT KNOWN'. Now consider a contact database that has a field for lets say Apt# or Street Direction such as N or S or ?? as an example. There are many, many instances where these fields would be left blank or empy: NULL | NOT KNOWN. When in fact the situation is known: the object has no such attribute; and in query or some other form of program logic the venerable NZ(subject, response) function may be used which would replace the NULL with a value. Or program logic and or error trapping would be used to handle such occasions. Which is an absurd waste of time and talent IMHO.
Therefore, if there is no applicable attribute to enter (something known) why not say so with 'N/A'? Else what we are saying by using 'NULL' is that we are building a dataset containing data that cannot be known. Kind of like explaining:
how do I set an entire colum to not accept nulls. example I have a colum that will be checkboxes. I want all the checkboxes to be in the unchecked state.
When filtering by form I suddenly get the words: Is Null / Is Not Null appearing in the drop down menu of all fields. I can then no longer filter at all? This is carried over to filter by form too!
When I export, or cut and paste the records into my backup database (filters working ok before I do!) the same thing happens!
I new to access and need some help, here is my problem. I have a query that gives data to a table, the only problem is that there is blank fields in the query and from what I read that is not a good thing when doing calculations. Here is the formula that I am using in the query DaystoCloseNonQSF: IIf([QSFNonQSF]<>"qsf",CalcWorkdays([DateReceived],[DateCompleted]),"") Then I need to get the average of the days that this formula returns, since there is blank fields it won’t. I hope that this makes sense.
I am trying to create a query whereby it will only show only those records when the x field is null. I also need a separate query to do the opposite, i.e. to show only those records which have x field not null.
How can I do this?
I know I need a statement on the x field but don't know what it is?
I'm trying to get this to work but is having a few problems. Hope someone can help.
SELECT * FROM MTL_Log WHERE (((MTL_Log.AccountingName) Is Null) AND ((MTL_Log.AccountingID) Is Null) AND ((MTL_Log.AccountingDate) Is Null));
I have the above right now. But it's not working right. I need the statement to pull all the records where AccountingName and AccountingID and AccountingDate are null and also if any of the field is null. Right now, if at least one of the field is filled in, the do not show in my report.
Any ideas on how to get this to where if any of the field is null then the record will show?
I have a table with a name field and five other fields. I want to create a query where it would tell me if the fields have anything in them or not. I created a query and put in the criteria "is null" and I got nothing in return. Then I put "is null" in the first criteria field and "is null" in the remaining field, but on the "or" criteria line. It worked, but I'm missing records because they dont add up between the number of records in the table and between the nulls and not nulls. Can anyone tell me why and what I am doing wrong please?
