Search results

I wouldn't combat it at all. I would construct my tables and relationships between them so I would not have to. I think we need to look at your overall design before anything else. That will tell the story. Can you post a screenshot of your Relationship window so we can see what the foundation...

Do yourself a huge favor and just let ACCESS do its job as designed. You are making it much more complicated and as a beginner, you don't need to do that. In fact, no one does. Just: Bind the form with a query. Don't use the table directly. Get rid of that stupid Save button. You don't need it...

Not with DateDiff. ACCESS reads the EventBeginDate & " " & EventBeginTime as a General Date which includes both date and time components. It's the only way I know to calculate hours between different dates and times when the dates span more than 1 day. I used Short Dates and Medium Times. ACCESS...

Suppose you have an event venue. Each event has a Beginning Date, a Beginning Time, an Ending Date and Ending Time. I have had success with the following formula used in a textbox to calculate the hours between dates and times: =DateDiff("n",EventBeginDate & " " & EventBeginTime,EventEndDate & "...

It seems more logical to have: Each tblAccount may have multiple tblCategory (Account Categories) Each tblCategory may have multiple tblTransactions Each tblTransactions may have multiple tblCheckCat (Check Categories to split transactions) So: tblAccount linked to tblCategory tblCategory...

I know and saw it, but from a different OP.

@martinr Did you get the answers you needed? Do you require additional help?

Does the theatre host different types of events (music, plays, lectures, movies etc.) or just one type? If yes, you will need an Event Type table. Can each event happen only once or on different dates? If yes, you will need an Event Date table. Can you host two separate events on the same day at...

Yes I understand. The whole thing here defies logic as Pat pointed out earlier. That said, I did some more experimenting and found that the OP's parent forms Data Entry property was set to Yes. With Data Entry set to Yes, you could not even scroll through the Parent form Record Source. I had no...

For the third and final time. Delete the parent forms BeforeUpdate event and you can select all the records you want in the sub-form.

As I said in Post #14, just remove the Cancel=True in the forms BeforeUpdate event and it will work. That line prevented you from selecting records in the sub-form.

I found the problem. You have Cancel=True in your FrmOrders BeforeUpdate event. Just delete the BeforeUpdate event and it will work. Private Sub Form_BeforeUpdate(Cancel As Integer) Cancel = True End Sub

Open the sub-forms record source to see if it is editable. Whether or not the Master/Child fields are present and active should not make a difference. You can have sub-forms without Master/Child links and still be a sub-form and still be editable.

Try changing the bound column to 3rd column with a 0" length. Just showing the first 2 columns in the dropdown.

Check the combo box properties settings. The first column may be a 0" length (as in the example above). If the combo box works as intended, then it is not really blank, the bound column is just not visible. In the example above, the first column is not visible but the second and third are, so...

So every single entry in every single record is checked for accuracy. And if someone enters a 5 instead of a 6 then the error is caught. Why not just let the original entry user correct their own entry mistakes as they work? They are the ones who know what the data entry should be from the...

What happens if a user enters and saves wrong information into your tables? Do you just let it go forever with no way of correcting it? I am a little surprised no one has told you this is a really really bad idea. That said, you might need to open the form in design mode first, then change the...

Set the Pop Up property to Yes on the forms property sheet

Learn how to use an Update Action query and set the values to Null or 0 or whatever you want.

It's annoying. I have to close the form when the report opens and then re-open the form when the report closes. I use the reports On Close event to re-open the form.