If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Name of form that invoked report
How do I find the name (in code) of the form that
issued the DoCmd OpenReport? Me.Parent.Name doesn't seem applicable, but I can't find the conceptual equivalent. Thanks, Bill |
#2
|
|||
|
|||
Name of form that invoked report
Bill wrote:
How do I find the name (in code) of the form that issued the DoCmd OpenReport? Me.Parent.Name doesn't seem applicable, but I can't find the conceptual equivalent. Thanks, Bill In the newest version you can pass the form name as an OpenArgs argument to the report. Otherwise there is no way to do it that is built in. Screen.PreviousControl.Parent perhaps? -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
#3
|
|||
|
|||
Name of form that invoked report
It seems I'm forever bumping my head on the lack of
OpenArgs in O2K.... Sigh! Anyway, the Screen.PreviousControl.Parent fails. If I put the calling form's name in a non-visible control in the invoking form, what's the syntax for referencing that control from the reports code-sheet? OR Perhaps I could test to see if the form is open? Which it would be if it was the invoking form. Bill "Rick Brandt" wrote in message om... Bill wrote: How do I find the name (in code) of the form that issued the DoCmd OpenReport? Me.Parent.Name doesn't seem applicable, but I can't find the conceptual equivalent. Thanks, Bill In the newest version you can pass the form name as an OpenArgs argument to the report. Otherwise there is no way to do it that is built in. Screen.PreviousControl.Parent perhaps? -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
#4
|
|||
|
|||
Name of form that invoked report
This is one of the situations where a public global variable can be used.
Have your form set the variable to the form's name just before calling the report, then have the report read that variable when needed. -- Ken Snell MS ACCESS MVP "Bill" wrote in message nk.net... It seems I'm forever bumping my head on the lack of OpenArgs in O2K.... Sigh! Anyway, the Screen.PreviousControl.Parent fails. If I put the calling form's name in a non-visible control in the invoking form, what's the syntax for referencing that control from the reports code-sheet? OR Perhaps I could test to see if the form is open? Which it would be if it was the invoking form. Bill "Rick Brandt" wrote in message om... Bill wrote: How do I find the name (in code) of the form that issued the DoCmd OpenReport? Me.Parent.Name doesn't seem applicable, but I can't find the conceptual equivalent. Thanks, Bill In the newest version you can pass the form name as an OpenArgs argument to the report. Otherwise there is no way to do it that is built in. Screen.PreviousControl.Parent perhaps? -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
#5
|
|||
|
|||
Name of form that invoked report
Thanks Ken, that's what I ended up doing.
Even though my clients are generally at Office 2000, can they in addition to that download a FREE copy of the Office 2002 executer and run a front-end back-end mde that was created with Office 2002? I would really like to upgrade my development to at least Office 2002. Bill "Ken Snell [MVP]" wrote in message ... This is one of the situations where a public global variable can be used. Have your form set the variable to the form's name just before calling the report, then have the report read that variable when needed. -- Ken Snell MS ACCESS MVP "Bill" wrote in message nk.net... It seems I'm forever bumping my head on the lack of OpenArgs in O2K.... Sigh! Anyway, the Screen.PreviousControl.Parent fails. If I put the calling form's name in a non-visible control in the invoking form, what's the syntax for referencing that control from the reports code-sheet? OR Perhaps I could test to see if the form is open? Which it would be if it was the invoking form. Bill "Rick Brandt" wrote in message om... Bill wrote: How do I find the name (in code) of the form that issued the DoCmd OpenReport? Me.Parent.Name doesn't seem applicable, but I can't find the conceptual equivalent. Thanks, Bill In the newest version you can pass the form name as an OpenArgs argument to the report. Otherwise there is no way to do it that is built in. Screen.PreviousControl.Parent perhaps? -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
#6
|
|||
|
|||
Name of form that invoked report
I am not familiar with an "Office 2002 executer"?
There is no free "exe" or "runtime" software for ACCESS 2002. If you want to use ACCESS 2002 features, and your clients don't have 2002, your only option is to purchase Office XP Developer Edition so that you'll have a runtime license for ACCESS 2002, and you then can package your application for installation on clients' PCs. However, note that a runtime version of ACCESS does not always exist well with other full installations of ACCESS, so you might see some problems if the clients retain ACCESS 2000 on their machines. -- Ken Snell MS ACCESS MVP "Bill" wrote in message ink.net... Thanks Ken, that's what I ended up doing. Even though my clients are generally at Office 2000, can they in addition to that download a FREE copy of the Office 2002 executer and run a front-end back-end mde that was created with Office 2002? I would really like to upgrade my development to at least Office 2002. Bill "Ken Snell [MVP]" wrote in message ... This is one of the situations where a public global variable can be used. Have your form set the variable to the form's name just before calling the report, then have the report read that variable when needed. -- Ken Snell MS ACCESS MVP "Bill" wrote in message nk.net... It seems I'm forever bumping my head on the lack of OpenArgs in O2K.... Sigh! Anyway, the Screen.PreviousControl.Parent fails. If I put the calling form's name in a non-visible control in the invoking form, what's the syntax for referencing that control from the reports code-sheet? OR Perhaps I could test to see if the form is open? Which it would be if it was the invoking form. Bill "Rick Brandt" wrote in message om... Bill wrote: How do I find the name (in code) of the form that issued the DoCmd OpenReport? Me.Parent.Name doesn't seem applicable, but I can't find the conceptual equivalent. Thanks, Bill In the newest version you can pass the form name as an OpenArgs argument to the report. Otherwise there is no way to do it that is built in. Screen.PreviousControl.Parent perhaps? -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
#7
|
|||
|
|||
Name of form that invoked report
Ken,
Sounds like a monumental bag of snakes to me. Thanks for the information, I'll store that under "Things one probably doesn't want to do". By the way, did you see my post about "Force a blank page"? Access Help is a little vague about how to do that and I haven't found how to do that in the OnPrint for the header. Bill "Ken Snell [MVP]" wrote in message ... I am not familiar with an "Office 2002 executer"? There is no free "exe" or "runtime" software for ACCESS 2002. If you want to use ACCESS 2002 features, and your clients don't have 2002, your only option is to purchase Office XP Developer Edition so that you'll have a runtime license for ACCESS 2002, and you then can package your application for installation on clients' PCs. However, note that a runtime version of ACCESS does not always exist well with other full installations of ACCESS, so you might see some problems if the clients retain ACCESS 2000 on their machines. -- Ken Snell MS ACCESS MVP "Bill" wrote in message ink.net... Thanks Ken, that's what I ended up doing. Even though my clients are generally at Office 2000, can they in addition to that download a FREE copy of the Office 2002 executer and run a front-end back-end mde that was created with Office 2002? I would really like to upgrade my development to at least Office 2002. Bill "Ken Snell [MVP]" wrote in message ... This is one of the situations where a public global variable can be used. Have your form set the variable to the form's name just before calling the report, then have the report read that variable when needed. -- Ken Snell MS ACCESS MVP "Bill" wrote in message nk.net... It seems I'm forever bumping my head on the lack of OpenArgs in O2K.... Sigh! Anyway, the Screen.PreviousControl.Parent fails. If I put the calling form's name in a non-visible control in the invoking form, what's the syntax for referencing that control from the reports code-sheet? OR Perhaps I could test to see if the form is open? Which it would be if it was the invoking form. Bill "Rick Brandt" wrote in message om... Bill wrote: How do I find the name (in code) of the form that issued the DoCmd OpenReport? Me.Parent.Name doesn't seem applicable, but I can't find the conceptual equivalent. Thanks, Bill In the newest version you can pass the form name as an OpenArgs argument to the report. Otherwise there is no way to do it that is built in. Screen.PreviousControl.Parent perhaps? -- I don't check the Email account attached to this message. Send instead to... RBrandt at Hunter dot com |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Move feild entries from form to form using global variables | JackCGW | General Discussion | 11 | November 14th, 2005 05:22 AM |
Requerying a pop up form to display in the main form | Jennifer P | Using Forms | 13 | April 5th, 2005 06:59 PM |
Help!! I'm running around in circles! | CathyA | New Users | 19 | December 12th, 2004 07:50 PM |
dlookup | miaplacidus | Using Forms | 9 | August 5th, 2004 09:16 PM |
Display Parameter from Form on Report | sara | Setting Up & Running Reports | 10 | July 19th, 2004 04:54 PM |