Search results

A MAPI (Messaging API) Client is (in simple terms) your email program. Outlook / Outlook Express / Eudora etc Check to ensure that all email configurations are correct etc. Brad.

Can you post the code for your "frame" that conducts the sorting?

Judy, I have only once come accross a similar MAPI error on a new workstation. Mine was caused by the MAPI client not being correctly configured to send email (regardless of Access interaction). Ensure that your MAPI client is correctly set up. As you are using Macros, there is no way of...

Have you considered inserting an "image" control to the form and enlarging it to the required size. (linked not embedded ;) ) Just a thought....

Vincent, Haven't worked with excel recordsets, but I would be trying Set rs = dbtmp.OpenRecordset("select * from [" & FIELDNAMEHERE & "$A1:C10]") Brad

Forgive my ignorance, but can't you achieve this by simply setting the "Tab Order" correctly for each page?

If at first you don't succeed, SEARCH again....... :rolleyes: http://www.access-programmers.co.uk/forums/showthread.php?t=66395&highlight=backup

First tip: Avoid using special characters (# $ % ^ &) in form / report / field / dog names. Use only A-Z, a-z, 0-9, and Underscore (_). (Whilst I am at it, don't start names with a number either). All in the name of good practice.

he he he, you are a harsh man.... You have to reference the Main Form / Subform_OBJECT / Subform_FIELD in that order eg: Forms!Main_Form_Name!Subfrm_ObjectName.FieldName Note: The Subfrm_ObjectName is the name that you gave the Subform object on the main form. It may or maynot be the...

Edtab's solution will definitely do the trick. Remember however: ** You will need to turn them back on after your procedure ** docmd.setwarnings false st=InputBox("New Entry") call DoCmd.RunSql("insert into table1 (field1) values ('" & st & "');") docmd.setwarnings true

Try: Private Sub MyFile_Click Application.FollowHyperlink Me.YourFieldNameHere End Sub Brad.

The OnClick of your original button will simply open up your popup form. This will also set that particular record (row) as the current or active record (row). The procedures of your Three options on the popup form can then reference any required information from the original form, regardless...

Without extensive coding, I think you will have trouble deleting the db itself, as the file will be open to execute the code, thus it won't be able to delete itself. Further to this concept: I assume you wish to promote (and hopefully sell) your project to this client. I would consider it a...

Unless you are happy (and it is appropriate) to use vbYesNoCancel as your options, you will need to create your own "pop up" form with your option buttons. You can then set your code to run from the selection on the new pop up form. Hopefully this will give you a start.

On your report design, select: File / Page Setup Decrease your bottom margin (currently 15.4mm) This will in effect give you more space to work with. (Thus you can lengthen your detail section in order to move the next record down). HTH Brad.

You will find some great date examples here: http://www.access-programmers.co.uk/forums/showthread.php?t=62570 I realise you said you are a newbie, but you should find a solution in Pat's example that you may be able to adapt. Cheers

Add the following to the AfterUpdate event of your text box: CommandButtonName_Click That will fire your command button code after text entry

I would suggest that this is caused by your default "0" being present when you click into field. "Bahaviour entering field" takes effect when you TAB (or progress) into the field, and not when you Mouse Click into the field. As a remedy, remove the default 0 from the field (at form & table...

Compliments to you Steve. Being a regular "Searcher" for forum answers, rather than just re-posting, I find it all too frustrating when a user has received a positive outcome, but never bothered to inform the forum as to the final solution. I hate reading through a 3 page thread only to have...

Weighing back in... We all seem to be singing the same tune here... Dave's solutions are for manipulating a Back End with a newly distributed Front End. Distributing a brand new front end = Easy = Happy Customer Distributing a "new" backend = Disaster = Phone call from solicitor :(