Search results

So, on further checking I note that I had put a 'Refresh' macro (RunCommand>Refresh) on the next field which must have also errored at the same time as the 3022 Error. I have now removed this command and the 2950 error now does not arise. Thanks to arnelgp and gemma-the-husky for their support...

Are you simply looking to access a sub-set of data in a particular table e.g. Male members of a Tennis club as opposed to Female members If so just build a single dropdown Combo box displaying just Male or Female options, then after making the required selection take the User to a Form that...

Looking at what you've pasted I'd say your mailmerge doc is looking at the TABLE not the query e.g. SELECT tblCHURCHES.LastMonth etc

Is it not possible to amend the MsgBox "LoftOrganiser does not permit duplicate entries to be made and has determined that this pigeon record already exists. Please modify or delete this entry." ... to include an "(IF" at the front and "vbYesNo) = vbNo Then ... " at the back end, with...

I have introduced the following code in the Onerror properties of a Form, to advise the user that he is attempting to enter a duplicate record. The code itself works well but perhaps doesn't go far enough in so far as the popup message it generates then only allows the user to click "OK"...

I deleted the shortcut to the DATABASE and instead created a shortcut to the MSACCESS.exe file with the path of the DATABASE appended to the Target file ...

... problem resolved.

OK ... should have mentioned that it's an ACCDR file that was installed together with MS Access Runtime 2007 but despite this the computer mistakenly kept trying to open the database with Adobe Reader. I checked the file association using "assoc .accdr" at the CMD prompt and to my surprise this...

Getting this message when trying to load a database ... the application was unable to start correctly (0x00007b) ... not sure it's an Access issue exclusively, anyone got any ideas what fix to apply (is it a Registry entry that's corrupted perhaps?). Many thanks (see attachment)

You're going to have to bring the Qualifications table as a linked SUBFORM of your main form. You'll need to add Employee ID to the Qualifications table, and this field will facilitate the necessary Parent/Child link between the MAIN and SUB forms.

A Select query on the data Table using the IsNull statement as the criteria on the Forecast Owner field. This will pull up just those records where Forecast Owner field is blank ...

So, in Table T_Master I can see that all that is currently recorded is the CIP you select from the drop-down field in F_Master, correct? Instead you want ALL fields in T_Master populated from F_Master, not just CIP? I must say I'm a little confused as to what you're actually trying to achieve...

1) I would simply store the full date in a DATE/TIME field, this way Access will always know the value is a date. 2) In the form that gets loaded, I would perhaps write some conditional formatting (e.g. red background) into each record's [expiry date] field based on a calculation whether the...

Not quite sure what you mean, Steve, but if you go into Design mode in the Form there's a Toolbox that will enable you to add various Form Objects such as Text Boxes and Combos.

I suspect that your specification will grow rapidly, what's the final objective for your project? You need, as best you can, to think of the end-to-end solution that you're looking for and this will help flesh out the data tables (and content) you will need at the outset. I suspect you're...

Quite a statement and not so, in my experience. In Report Design mode you can achieve many variants, until you settle on your final, preferred, design.

Are the pictures all absolutely required? I'm afraid I don't know of any shortcuts but would however recommend that you LINK rather than EMBED the pictures as there are many synergies associated with displaying pictures this way.

You could perhaps store a 'dummy' record (with mostly blank fields) in the data Table and get your Query and Macro to print out this 'dummy'?

Yes, this is a good way to prevent blank records. Equally, you could put 'Required' flag on the Field in the actual data Table and/or back this up with a cleanup query that deletes blank records each time you Load the Form.

OK ... If you can zip and upload the Database (in Access 2003, preferably) I can take a quick look and add the required query and/or form for you.