Search results

Another Approach... This should be a little more elegantPrivate Sub Contractor_AfterUpdate() Dim boChoice as Boolean 'The following evaluates to either True or False boChoice = (Me![Contractor] = "GECC" or Me![Contractor] = "SVDP") Me![DIMAFlatAddress].Enabled = boChoice...

It looked as if it would work, but... It compiles OK, but then at runtime it gives an error: Runtime error '2465': Application-defined or object-defined error. And not only that, it doesn't change the property!

Greetings to all I've searched and hunted and experimented, but to no avail... From a pop-up form, I would like to update the property of a label on one of several other forms. The circumstances of the moment will determine which form's label is getting updated. I can't figure out how to...

Should be easy. Create an update query based on that table, add the field you want to update (MAIL), and update it to N. Every time you open that query, it will set all the MAIL fields to N. You can open the query on the start of that form, or place a button on your form which opens the query.

Perhaps you could fix it by placing a label beneath the button: "Click Hard" That's how we fix things in the movie business.

You should be able to make some pretty good application stuff with Office 2000 Professional. There are some nice features you get with the Developer's Kit, such as the ability to easily use Access built-ins like Open File Dialogs, but I got a long way before I found the Developer's kit a...

I believe he's right. The MDE file isn't locked. It's supposed to be compiled, lacking all the text and editing data which would allow you to work on the DB.

You stump pretty easily. I don't want to sound all mean and nasty or anything, but you could experiment a little on your own. Or you could look up public variables in the help files or in some book. Or you could re-read my original post and see if there's something you missed. Or you could...

You've got to dimension the public variable. At the top of any module block, right after the Option Explicit statement, add: Public pPubStringName as String That creates the public string which you may use globally.

Too much equality. The above solution is essentially correct, but it has too many equal signs. Only one equal-sign is required at the beginning, the value which follows the conditional commas will be returned. To use the same code as jfgambit gave, you'd make it: =IIf([check1]=Yes And...

You're almost there. I thought you were using the global variable in a query. If you're just using the value in a form or report, it's simpler. You may delete the function: Public Function gGlblStringName() and all that comes with it. In the OnOpen event of the form (or report) in which you...

Look up "TransferSpreadsheet" in Access Helpfiles.

As it is currently constructed, what event triggers the message box?

1. Create a new module with the following: Option Compare Database Option Explicit Public pPubStringName as String 2. Then add this function to the same (or any) module: Public Function gGlblStringName() As String gGlblStringName=pPubStringName End Function Save and close the module(s). 3...

I'll make a stab at some answers. First, aside from browsing, I've found that the search functions for this forum are incredibly helpful, if you can find the right words to search for. Often I find several posts which are circling the question I have, if not outright answering them. As for...

Is there a compelling reason for you to concatenate these two fields into one textbox? If not, you could simply keep the two textboxes separate, and everything in Textbox1 will remain aligned. Also, I would guess that with the code you've included, Textbox2 will double in size every time...

Another approach would be to create a global variable. Before opening the report or closing the form, assign that value to the global variable, and have the report use the global variable rather than the value directly from the form.

Could you explain a little more? What do you mean by manipulated data? Is it not in the query you're exporting? An example?

I'm not sure what's causing the problem, as I'm using this code pretty much as-is, but you could add the SelectObject as below: Dim NumCopies as Integer NumCopies = 3 DoCmd.OpenReport "ReportName", acViewPreview DoCmd.SelectObject acReport,"ReportName" DoCmd.PrintOut acPrintAll, , , ...

Try this: Dim NumCopies as Integer NumCopies = 3 DoCmd.OpenReport "ReportName", acViewPreview DoCmd.PrintOut acPrintAll, , , , NumCopies DoCmd.Close acReport, "ReportName" This should cause it to print 3 copies. You set the variable NumCopies before you begin.