Search results

Create 2 fields, one for each score then just concatenate the fields into one field in the query/form.

As far as I am aware, Access does not support Transparent graphics, hence the display you are encountering. A sort of work around this is to fill the button face with an image which will look a little better but you will still see the beveling in a different colour.be

Sorry, just a misquote from me - I only know and have developed with Access but interested in seeing how the pro's view access as a 'tool' or a serious development environment. Also Is something I thought I'd never see in here. :D

Pat, I was interested in Access being a useful prototype. What do you find (or work on) as the preferred 'real' application model?

Thanks

Thanks Pat and EMP for correcting me. :) I obviously had an erroneus understanding of the behaviour of IIf in the Field: cell of the QBE grid. My explanation made sense to me (although incorrect) but Pat's and EMP's explanations, although I understand both, seem to contradict one another re...

I suppose I'm just lucky at work not to have computers with speakers then:p

The usual syntax of the openform method will not work in this manner but a little cheat will, but it depeds on the recordsource of the subform. In general, you can recycle the existing code but rather that passing the strCriteria as a criteria, pass it as openags to the form you are opening...

I'm sure there is an option in Tools -> options -> general. Something like "Provide Sound with Feedback" You can disable this - but I'm not sure if this will stop the beeps. Failing that, A pillow, carefully taped to the side of the computer to muffle:D

Essentially, the QBE grid is a graphical representation of the SQL statement but presented in an easier to understand fashion. You have bypassed that by essentially putting the what access would do normally into the Field part of the QBE grid. Access cannot quite decipher the IIF in the field...

Why do you want to disable the cursor in the box?

Sorry, I just assumed it was in the field box. Try the same statement in the Field box rather than in the Criteria box.

Do you have to use DLookups? Can you not use a query to populate the form and pull the info into the query from multiple tables?

Have you tried this? IIf((Date()>#5/19/2003#) And (Date()<#6/17/2003#),[reports.RepPer]=Between #5/20/2003# And #6/16/2003#,#9/4/2003#)

This depends on the data structure. After importing, how is the table structured and which field(s) are the asessments stored ie is there a field for each assessment?

All you need is a simple select query with a couple of criteria. In the start date field you will set the criteria to >= Date() and in the End date field <= Date() In the ContractorID field, set the totals to Count (press the sigma button on the toolbar to enable totals) You can then run this...

If your combos are cascading, you will need to requery then on the Form_Current() event (I'm sure) otherwise they will not show the records relevant to the parent combo. Search here for cascading combo and look for a demo posted by Hayley Baxter - that should point you in the right direction on...

Create a textbox on the main form with the controlsorce set to =Forms!MainFormName!SubformName.Form!ControlName On the master/child links of Subform2, set the child link to the field on the subform but set the master to the control you have just set up on the main form ie Master =...

A little more detail would be appreciated. How do you want to count these contractors? Do you want to show only the active contractors on a given date? Where and how do you want to display the information (Form/Query/Report)

No the post just creeps in at number 11 :p This is very easy to do using a combo box rather than a textbox. That way, you can store the ID, but show the actual text description. Right Click on the existing textbox where you have the BCode stored, Change To -> combo box. In the rowsource...