Search results

Do you need to display BOTH the code and description? If so you might consider using a List box instead of a combo. If you only need to show the description, then just set the first column (the code) to 0" in the column widths. A combobox will only display the first non zero width column. If you...

Assuming you want to the records to be added with the first month of the lease, I would do it like this: Dim strSQL As String Dim dteCurrmth As Date dteCurrMth = Me.txtLeaseStart strSQL = "INSERT INTO table (LeaseID, LeaseMonth) " For i = 1 to Me.txtNumMonths dteCurrMth =...

A more accurate way of determining age is: Age=DateDiff("yyyy", [Bdate], Now())+ _ Int( Format(now(), "mmdd") < Format( [Bdate], "mmdd") ) If you need to use a different date then the current one substitute it for Now(). But that only solves part of your problem. What you need is...

Date/Time fields can store both date and time. The date is stored as a serial number counting the days from 12/30/1899. The time is stored as a fraction of a day where .25 = 6 hrs. Therefore, if you only store the time (decimal) then you can't do accurate time span calcs. If you store the date...

Fields should only have a number format if they will be used in mathematical calculations. Otherwise they should be text. Also there is some debate over the use of natural vs surrogate keys. A natural key is data that has some meaning to the user. Like a telephone number. The problem is that...

As Colin suggests what you are after is a Users Manual. But your boss also wants a schematic as well. So you use the Documenter for the latter. For the users manual, find a screen capture utility and use screen shots to detail how to use the app. I've attached a sample of one of the User guides...

First, I don't recommend composite primary keys. They generally are more trouble then they are worth. I recommend using an autonumber as your PK. If you need to insure uniqueness in a combination of fields, then use a unique multi-field index for that. Second, I would use a DLookup here because...

To add to what Neil said, if the form is bound to the table, then why run an update query? Bound forms are automatically updated as the values in the controls are entered.

None of the above. the first two would violate normalization rules. The last is unnecessary. You add a table: tblPayments PaymentID (primary key autonumber) PropertyID (Foreign key) PaymentDate PaymentAmount This is all you need. You do NOT need to store the total of poayments, that's a...

I agree with Rich. You should NOT be storing a balance. As a general rule we do NOT store calculated values. I assume you are storing the annualized premium for each policy somewhere. To calculate the balance, you add the total payments and subtract that from the annualized premium.

The issue here is one of normalization. Normalization is an essential design technique for relational databases. The rules of normalization were first set down about 40 yerars ago and have not radically changed since then. The main purpose of normalization is to reduce or eliminate redundant...

This really depends on what your needs are. You can restrict the display of any date value to show only month or month and year, but you will still be storing the full date. I would recommend this. However, if you want to just store the month or mth/year you would need to use a text field to do...

Can you explain what you mean by document? Access includes a documenter wizard that will give you a printout of all the fields/tables and much more.

Why not show us what you got. The VBA Help should have given you sample code.

Applause. My compliments on your perserverance and success.

Setting up relations does NOT automatically populate foreign keys. That's not the way relations work. A record should be added to a child table only when there is data to go in that record. Generally, in a situation like yours, you use main/sub forms to enter data into parent and child records...

The error message means that you are using the ME qualifier somewhere in error. Is there a Debug choice when you get this error? If so, what line of code is highlighted? If not, you need to to find where you have the erroneous ME.

Detail the problems and we'll try to help.

First make sure the Column Count for the Cat Combo is set to 2 and the Column Widths set to 0";1". Second, in the GotFocus event of the Products combo use the following code: Me.cboProduct.RowSource = "SELECT ProductID, ProductName FROM PRODUCTS WHERE CatID = " & Me.CboCat & ";"...

Could be a data type mismatch or conversion of some sort