Search results

Surely you want to set the cboProjectName to Me.OpenArgs not [ProjectName] ?

Does your control have the same name as the underlying field? This will confuse the Access gnomes. Change your textbox name to txtDateReceived and try again. Me.txtDateReceived.BackColor = vbYellow

I think. xlsx.SaveAs FileName:=(strpath), FileFormat:=56 should be objXL.SaveAs FileName:=(strpath), FileFormat:=56

Try , (commas) as separators instead of ; (semi-colons).

Check that you have a default printer installed - no printer = no reports

Alternatively you could use a label for "FAMILY AND FRIENDS - NAMES AND ADDRESSES" if you want the same text every time. Set this in the caption property of the label.

http://www.asap-utilities.com/index.php ASAP Utilities has a tool for stripping out spaces in Excel worksheets.

The code provided goes between the Sub Form_Current() and End Sub code stubs.

You should not store the product name in the InputProduct table. You only store the ProductID as a foreign key - this leads you back to all of the product details in the Masterproduct table. Normalisation 101.

Changing backcolor of a textbox is possible using conditional formatting. Changing the .visible property of a button is NOT possible in a continuous form (unless every instance of the button hiding/reappearing is acceptable (which I doubt))

It can be done using API calls http://vbnet.mvps.org/index.html?code/comdlg/messageboxex.htm Complicated though! A custom form might be easier.

Make sure that your database is in a Trusted Location otherwise no VB coe will run.

shabbaranks You have a couple of ticking time-bombs in your db. You are using reserved words for field names - Hour, Project and Description. This may explain why you are having trouble with your code.

Leaving aside the potential normalisation issues AT&&T (note 2 ampersands) will display a single ampersand in a label's caption. You cannot use it as a field name as has already been posted.

I presume this message comes up when you close the form? What is your code to close the form?

Use the Find that is built into to the VBA IDE?

Does it work correctly in Preview mode and in Print mode? Report view does not run code and other features so that might be the problem.

Your foreign keys should not be autonumbers. Your Primary keys should and, in answer to your question, if you have an autonumber primary key then cascade updates are irrelevant.

Personally, I would put the DoCmd SetWarnings True after Exit_cmdRun_Click so that warnings are always turned back on, even if your error-handling block runs. Just my two penn'orth.

Oops, wrong thread - sorry! (Or has something been edited?)