Search results

Hi Sonic, [Code No] as far as I understood, should always be unique, however in the table it is set to Duplicates OK. I've no idea why this is the case. As you showed, [Code No] is infact text, which solves my issue with the query, which is great. Thanks for your help.

Thanks for this info, I'll definitely take a look at these articles.

Hi Moke, Thanks for pointing this out, I had assumed [Code No] was a number, but as you've showed it is in fact stored as short text. This has solved my issue to do with the query I've been wanting to create. There was one table with a foreign key related to EquipID, but I don't believe it's...

Hi Gasman, As someone pointed out above, I have mistakenly assumed CodeNo is a number due to the name, and instead it is short text. I created a new table with CodeNo in it as a number, and created a relationship between the 2 tables. When creating a query, I was getting a 'Data mismatch in...

Hi Ranman, Despite CODENO only ever in theory being unique, because no 2 pieces of equipment should have the same CODENO, for some reason Yes-Duplicates OK is selected for this value. I think this was an error that has been in place since the beginning of the database.

Hi All. I have taken over a database and I have come across an issue with one table and its primary key that I don't understand. We have a table called [Import Equipment] that stores information about all of the equipment that we own. Each piece of equipment is given a unique [Code No], and we...

Hi Gasman, In the new query that I created, I only included [Code No] and I forgot to include the fields [Institution] [Owner Department] [Directorate] and [Location]. Since adding these fields to the query it is now working OK. Thanks for your help. For n = 1 To TotalRecords REC2.AddNew...

Hi Pat, I'm not too sure why the records get created ahead of time, this was in place before I took over the database. The main reason I can think of is that the automatically generated job autofills a lot of information that the user would normally have to fill in, which speeds up the process...

Thanks Ranman. I have done what you said and it works perfectly.

Hi CJ, Since your message, I managed to find out an issue. The query PPMAutoJobs was not pulling up any records, which is why the "No Current Record" message was showing. I have since created a new query called PPMQueryPPMCreateJobsStep2 which now works perfectly. I have substituted this query...

Hi All. I have a database for equipment, the majority of which, requires a yearly service. When equipment is being serviced, a job is created and service details are completed for the equipment. I want to be able to automatically create a job (record) when the equipment is within 28 days of...

Hi All, I've got a command button that was working OK in Access 2010, but since upgrading to Access 365, I've been received a 'No Current Record' message. The full code behind this command button is included at the bottom. I have done some process of elimination with the code an found that the...

Hi Pat, I think I may have used the wrong terms to describe what happens. When I say duplicate record I mean, a new record with its own unique job number (Autonumber primary key) but with the same Code No. In theory there should never be 2 records that are not complete, with the same Code No...

Hi Pat, We have around 15000 devices in our database, some of which require a yearly service. When a device reaches within 2 weeks of its yearly service, a record (job as we call it) is automatically created with various information. This speeds up the process of filling in the record. Also it...

Hi All. The code was written more than 20 years ago so that may be why it is so complicated. I have taken the database over in the last year. What I have decided to do to make the process a little easier to understand for myself, is to do the following: Create a non-visible command button to...

Hi All. I've updated my DB from Office 2010 to 365 and the accmddeleterecord is no longer working. When a user creates a record for a device, code runs to check whether there is already an outstanding record for the same device. If there is an outstanding job, the user is then prompted...

Hi All. I have a subform called ContractsEditSubform that is based on a query called QueryContractsSubform. It had always worked completely in my .mdb used in Office 2010. Due to an IT update to Office 365, I imported the database in to a new 64bit .accdb. Since doing so, it says that my...

Using the following "Where Condition": "[Manufacturer Part No] = '" & [PartNumber] & "'" It brings this popup box up: If I enter a valid part number in, it just opens the Storemanager form but does not apply any filter. I have instead entered the following "Where Condition"...

Hi Gasman, Please see the post above. Thanks

Also just in case I weren't clear. The Manufacturer Part No is stored in a table called ImportParts. The PartNumber is stored in a table called NSRSubform.