Search results for query: *

Maybe look at the Duplex Property of the Printer object? -- Jonathan

Recent thread discussing sending e-mail... thread222-734914. There are quite a few threads in this forum if you just do a search for sending e-mail. As far as command line arguments, take a look at the Command$ function. Here's a thread on it... thread222-684007. -- Jonathan

I should have mentioned... replace DataReport in the above code with the name of your DataReport. It's just like any other object or control... objName.xxx. -- Jonathan

You can set the label's caption equal to a control's value, yes. -- Jonathan

This can be done using something like... DataReport.Sections("ReportHeader").Controls("lblFillMeIn").Caption = "Filled In" Of course, you'd need to change the section and control names accordingly. -- Jonathan

Don't harcode it? Maybe store the path in an outside file or in the registry? -- Jonathan

Well if there's only 1 of 3 options for an output, wouldn't you only have a need for 3 conditions rather than 64? -- Jonathan

You could use the Format function to force your expression into a certain format (i.e. Format("0","00") returns "00"). -- Jonathan

For those interested, there was a paper written by Wulf and Shaw in 1973 titled "Global Variable Considered Harmful." I had difficulty finding it online anywhere other than in the ACM Digital Library. http://portal.acm.org/citation.cfm?id=953355&jmp=references&dl=ACM&dl=ACM Some of...

I'm not a heavy Access Report designer myself... my first thought would be to add a Group Footer band. My initial reply was only to redirect others who might wish to respond to a post that already had responses. Good luck. -- Jonathan

thread222-747042 -- Jonathan

Perhaps this might help... http://www.andreavb.com/tip030001.html -- Jonathan

Unfortunately, I think DataReports are limited to only 8.5" x 11" in size. Someone please correct me if I'm wrong. -- Jonathan

ReportWidth deals with the width of the report. Width deals with the width of the print preview window's size. -- Jonathan

Check for an error after you update the recordset. Is there one? Comment out On Error Resume Next to see what is happening? I don't believe you're handling error 3265 correctly. My ADO Error Reference is saying that a field is probably misspelled. If that's the case, you're not handling the...

It sounds like the structure of your report doesn't match that of the data source. My first thought to approaching the problem would be to create a new DataReport and power it with the same data source as your existing report. Then on this new DataReport, retrieve the structure of the data...

Nicely done. Another something to tinker with. :) -- Jonathan

From looking at what has been posted, it looks like both tables are related by the Emp_ID field. If the Emp_ID field is the Primary Key and an AutoNumber type in both tables, that could most certainly cause problems when relating the two tables on that field. However, that will not prevent...

Could you do something like this for your update? 'Update existing records strSQL = "UPDATE tblA AS a, tblB AS b SET a.eHC = b.HC, a.eMC = b.MC, a.eODI = b.ODI, a.eOTH = b.OTH, a.ePA = b.PA, a.eSFL = b.SFL WHERE b.Emp_ID = a.Emp_ID" -- Jonathan

For once I was told to RTFM rather than telling someone else to do the same... heh. That serves me right. Should have checked the documentation first where it states the ampersand converts a non-string to a string variant. Thanks to the both of you. -- Jonathan