Hi Jon.N
I don't really understand what the problem is ... assuming your subform and main form are linked with the correct shared field in the Child/Parent links, won't opening the main form at the correct record automatically bring about opening the subform with the required associated...
Hi callumwatson
Apostrophes cause a problem as they are used to indicate in coding a change from code to a literal value (or from a literal value back to code) e.g.
="Today's date is " & Date()
The first part is a fixed value (within the normally double quotation marks - but single can be...
Hi thhakala
I would have thought that it would be preferable to use criteria in your queries underlying the report and subreports (I am assuming your report and subreports draw on queries rather than the table). With queries and parameters set up properly I don't think it is necessary to use a...
Hi OliviaS
Create a many to many relationships using 3 tables (two to store data - tblKit and tblPart, one to link the two main tables together-using the Primary key from tblKit and linking it to the Primary key for tblPart).
See this link below for a description of how to go about this for a...
Hi wrek
How about having a tabbed form with different pages with the subform being located on one of the tabs/pages. You can then set the subform's Source Object to blank (i.e. nothing typed in for that property) so it is an unbound control.
Then put the following in the tab's On_Change...
Hi Talismanic
Interesting question!
I may be wrong on this one but it always seems to be the case that the form/window when viewed in design view will have the normal headers/footers (if selected) and the detail section but also some space given for the menu bar and tool bar when in design...
Hi jayme27
Have you thought about not allowing the key fields in the tables (e.g. Supply Cost and/or POLCost) to have a null or zero length entry (i.e. in the table design set the field "Required" = Yes and "Allow Zero Length" = No). You could also put in a default value for these key fields as...
Hi thhakala
I don't think you can do what you want within a straightforward report and grouping set up, as this would mean repeating the same record within various groups.
However, why not set up various subreports - so you would have a subreport that was based on TF1 followed by a subreport...
Hi btrflym
Glad you got it sorted!
By the way you do not need to be so formal - call me Rich (well, I am Rich by name, if not financially rich!).
Best wishes
Rich Gorvin
Hi btrflym
I agree with Rich's advice - so even if changing Date as a field name to something else (eg EntryDate) has not solved this problem, it will have saved from other problems later on!
Have you tried Format([EntryDate],"mmmm yyyy")?
If that doesn't work have you checked your...
Hi Pedro
Unfortunately you still have me confused ... how is it that four cars made in one day results in -4 wheels? Can anyone else see what Pedro is trying to achieve here?
Rich Gorvin
Hi pacgoncalves
I am not too sure what your question is about, but perhaps it is on the topic of many-to-many relationships.
Access normally allows tables to have a one-to-many or a one-to-one relationship between two tables. In the situation of car parts you can put one type of part in many...
Hi deepbreath
I agree with Rich (well, with that great name what would you expect) - but I'd like to add the following points.
If your first field is sometimes likely to be empty or blank then your field2 could start with a "leading space". Try this instead:
=([Field1]+" ")&[Field2]
FYI the...
Hi Christy
Yes there have been other posts on this topic and I will add a link below to one of them. However, a good design principle is to always work to the lowest resolution that any user will have on their PC when creating your database. This is part of the planning and consultation...
strange strange strange
This posting seems to appear twice ... double strange, strange, strange!
How have you linked the two tables? What is your Primary Key in your first table - have you used a similar data type in your second table for the Foreign Key?
What sort of relationship have you...
Hi shbond
First thing - definitely don't store dates as a text format, it will screw up any possibility of performing all sorts of calculations, sorting, etc.
In the text box concerned set the Format property to mm/yy. That's all!
HTH
Rich Gorvin
Hi Susan Jayne
Just create unbound text boxes in your Report Header and in the Control Source put the parameter wording used in the underlying query - e.g.
=[Enter Start Date]
and for the end date ...
=[Enter End Date]
HTH
Rich Gorvin
What effect do the margin settings on a subreport have when that subreport is embedded into a main report?
Thanks.
Rich Gorvin
[This message has been edited by Rich@ITTC (edited 06-22-2001).]