Search results

beyond all reason

I would check the references on the computers that don't play ball.

Thanks Doc Man - better explanation than I could muster up! Sample Db is as you say except has an additional field for reference ie Author / Referee etc. with compound primary key. I found it easier to create than explain - now what does that make me again - a visual teacher (something like...

I think I follow. You have set default values for your operation and therefore are only adding data to the patient and procedure forms? These will only be committed if you actually enter the operation record and start typing. If your relationships are set correctly, this should not be possible...

Looking at your description it really depends on your data structure. Rather than storing Author1 Author2 etc, use a junction table to create a many to many relationship which makes querying soooooooo much easier. Have a look at the (very) ruf and ready example I have attached as an example.

How are you using this procedure? (and what does it do for that matter) If it sets a value, it is far better to set the value of a unbound textbox to a function that can evaluate the value for you or set the value via VBA code on one of the form's events. You can then refer to the unbound text...

I'm assuming if you are going to such lengths to detect a button press on a report, you must have more than one button? Is there any reason why you cannot use a customised toolbar rather than go to such exquisite methods?

It is not likely that they are being deleted when saved (unless someone is deleting them :eek: ) but more likely that they are a) being overtyped b) not being saved in the first place due to some data violation eg duplicate key values etc. I suggest look at (b) as your first problem (look at...

You need to use 2 queries to be able to do this. Find Attached an example of this. You do need to sort out your structure as you should not use text as an ID - use an autonumber instead - you are violating the basic rules of normalisation and will run into problems later.....

2 Questions. Why are you saving the record via code as when you move to a new record, the changes made are committed to the record anyway. (And there is more efficient code than that menubar stuff) What records do you want creating for the subform? If you move to a new record on the parent...

You do this by using the criteria box of the query. However....... If you want to change the products you want to filter on, then it means having to go in and change the criteria every time. What is slicker is to use a multiselect list box to select the criteria and using that to populate the...

Apart from being a longwinded query, this line (and the 2 others like it) look a bit fishy to me. I have highlighted the bit I am suspicious about: "AND [ADD 1] Not Like '*'*' AND [ADD 1] Not Like '* *'" & _ Counting up your ', There is an odd number (I think) - obviously these must be paired...

Change [FORMS]![frmInvoiceDetail]![Cat] to Forms![tblInvoice]![frmInvoiceDetail].Form![Cat] in your query powering the Product Combo You have to reference Subform controls in a more explicit way as shown above. If you are not sure of the syntax, use the expression builder.

Try surrounding your dates with # ie strWhere1 = strField1 & " < # " & Format(Me.txtEndDate, conDateFormat) & " # " On a side note: If you are using between, should you also not be using <= and >= in the other evaluations?

Hi Rymer, Long time since I've posted an answer so I may be a little Rusty ! Your form structure does not match your table structure, as you need nested subforms ie Form = Invoice Entry Subform = General Form = General Subform = Machine. You do not necessarily need to show the linked ID...

I did tell you it would go pear shaped :rolleyes: How does it become unpredictable and how are you trying to use it?

This follows on from your previous query and dcx has highlighted something I mentioned before ie, not naming fields Date, Time etc as these are reserved words. In general, follow the same question you posted before as you have had a duplicate answer for the same question. Anyway, less of the...

2 things. Date is a reserved word in access so do not use it for field or control names. To make this work with date fields, you need to change the data structure and syntax of your DCount. Correct Syntax would be Num: DCount("*","ABC Query","Date <= #" & [Date] & "#") However if you have 2...

It doesn't really matter until you try to do what you are doing. Access then gets confused and throws all it's toys out the pram. In general, it is better to rename your controls with a prefix eg cbo for combo txt for text chk for checkbox cmd for command buttons. It is called Leszynski Naming...

2 things Make sure that the form controls have a different name to the field names Make sure that you are summing values supplied by the query and not calculated controls on the form