Search results

The way I do this is to add a field called Increment. I then use the Before Insert event to set the value for a hidden control on my form bound to that field to: =Nz(DMax("[Increment]","table","[ReqDate] = #" & Me.txtReqDate & "#"),0)+1 As for the Reference number, this should NOT be stored...

No. The question is whether the ID number is being used to link to records in another table. If not, then there should be no problem in having a new autonumber generated. If there are related records, then you will need to add a temp field called OldNumber and fill that with the OldID. Then...

If I follow you will be appending new frecords from the warehouse on a weekly basis. You want to tag the records so you know when they were appended. The easiest way to do this is to add a field to your table call it CreateWhen and set the default value to =Date(). Then, whenever you append...

duplicate post please delete

Why create a table? A query can do this very easily. Just join on Field 1, Include Field 1 from one table and field 2 from the other tables.

30K records is not a problem. What I would do is link to the Excel tables then do an Append from the Excel tables to your Access table. You can do your massaging of the data in the Append queries (one for each supplier).

Could it be that there are 600 unique addresses? But that 17000 records use one of those 600? Lets look at it this way. You have a table of names. There are 10 records. All the last names are different, but there are 3 Toms, 4 Dicks, 2 Harrys and 1 Jane. So you have 4 unique first names, but 9...

I'm not sure if your structure or your terminology is incorrect. Categories shouldn't have FIELDS (Floors | Exterior | Interior) but VALUES. The same for Subcategories. What you are talking about is a standard technique called Cascading or Synchronized combos. If you search here you should...

This is more a procedural issue. Users should be instructed to not do this. Its not something that should happen accidentally. But you can put the FE in a READ only folder on the server. Then have the automated deployment copy from that folder.

I do not recommend compund or composite keys for this very reason. I recommend that you use an autonumber as your Primary key for each table, then use that as your foreign key in the related table.

As Pat has said, you have to use one query to get the one record you want and then another to filter for that one record. That's what using an IN clause as I suggested does.

Ok, then just create a form using the Wizard. After the Wizard does its work, go into Form Design mode and set the Data Entry property to Yes. This will restrict the form to only allw new entries. Next, delete the control for the CompanyID and use the Combobox wizard to create a combo to select...

Enter the IN Clause I gave you as the criteria of your query.

glad to assist

Just use the Form Wizard to create the form. Its not clear whether you are adding new data or updating an existing record. I'd need to know to suggest anything more.

You are describing different things. Data entry is a part of your process. There is NO reason to lump it together. Even if you are getting the data from the 3 companies at the same time. All you need is a form where you select the company and either enter or update the data for that company...

I assume that the last record is the one with the most current date? In that case, you can use a subquery to get that one record: SELECT * FROM table WHERE RecordID IN(SELECT TOP 1 RecordID FROM table ORDER BY dateField DESC);

make a new query based on this one one and add a column: AvgChat: [SumofTCT] / [SumOfNC]

Actually there are several flaws. The ONLY time when it is valid to repeat info (other than the foreign key) inb a related table is when you are trying to freeze time sensitive data like the current price of a product. There is NO way that that your situation is "the only good choice". Its...

Requery the second comob after a selection is made in the first one.