Re: Error Message Help

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

The macros that run the buttons in question are as follows:

Properties
Container: Scripts
DateCreated: 12/12/2006 10:24:45 AM
LastUpdated: 12/12/2006 10:24:45 AM
Owner: admin
UserName: admin


Macro: Proj Lst Entry
Description: Open Project List and Project Entry Form
Action: SetWarnings
Argument: Warnings On
Value: No

Action: OpenForm
Argument: Form Name
Argument: Proposal and Project Input
Argument: View
Value: Form
Argument: Filter Name
Value:
Argument: Where Condition
Value:
Argument: Data Mode
Value: Add
Argument: Window Mode
Value: Normal

Action: RunApp
Argument: Command Line
Value: "C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE"
"\\Big_brother\procad designs server\JOBLIST\Project List.xls"

Action: Close
Argument: Object Type
Value: Form
Argument: Object Name
Value: Enter Proj Prop on Lists Options
Argument: Save
Value: No

Action: SetWarnings
Argument: Warnings On
Value: Yes
_________________________________________________________________
Macro: Prop Lst Entry
Description: Open Proposal List and Proposal Entry Form

Action: SetWarnings
Argument: Warnings On
Value: No

Action: OpenForm
Argument: Form Name
Value: Proposal and Project Input
Argument: View
Value: Form
Argument: Filter Name
Value:
Argument: Where Condition
Value:
Argument: Data Mode
Value: Add
Argument: Window Mode
Value: Normal

Action: RunApp
Argument: Command Line
Value: "C:\Program Files\Microsoft Office\OFFICE11\EXCEL.EXE"
"\\Big_brother\procad designs server\JOBLIST\Proposal List.xls"

Action: Close
Argument: Object Type
Value: Form
Arguement: Object Name
Value: Enter Proj Prop on Lists Options
Argument: Save
Value: Yes

Action: SetWarnings
Argument: Warnings On
Value: Yes

________________________________________________________________
Macro: No Lists Entry
Description: Open the Entry Form, No Lists

Action: SetWarnings
Argument: Warnings On
Value: No

Action: OpenForm
Argument: Form Name
Value: Proposal and Project Input
Argument: View
Value: Form
Argument: Filter Name
Value:
Argument: Where Condition
Value:
Argument: Data Mode
Value: Add
Argument: Window Mode
Value: Normal

Action: Close
Argument: Object Type
Value: Form
Argument: Object Name
Value: Enter Proj Prop on Lists Options
Argument: Save
Value: No

Action: SetWarnings
Argument: Warnings On
Value: Yes
__________________________________________________________________

The above info was copied directly from the "Print Macro Definitions Report"
(Other than the formatting).

The form that is being used here - the "Proposal and Project Input" Form
doesn't depend on any queries. It is strictly a data entry form for the
"Tracking" Table. I double checked the object dependencies to make sure I
wasn't missing something on this point.

The pop-up is also not based on a query. If you would like the coding for
that, I can post that too, although I don't think the problem is there
because the error only comes up after you click one of the buttons that runs
the above macros.

The only "spelling mistake" that I found while copying this information was
an "L" in "EXCEL" in lower case in one of the RunApp Actions. I fixed it in
the database, and it didn't make a difference - so that wasn't it. I fixed
it in the info above as well. (I know Access can be finiky like that - it
was worth a try).

Thanks for you help, Steve. Let me know if you need more information.

Jennifer

"Steve Schapel" wrote:

Jennifer,

Can you please post back with some specific details of the actions in
the macros? And also, if the forms are based on a query, can you post
the SQL view of the query? Thanks.

--
Steve Schapel, Microsoft Access MVP

ProCad Jen wrote:
I have created a popup form which offers three command buttons. Each command
button gives the option to open a specific Excel spreadsheet and adjacent
Access data entry form. The third button closes the window if you opened it
in error (backdoor). Each of these three buttons are keyed into their own
Macro. When you click on either of the two option buttons, I'm getting the
error message

"!ProCad Designs Ltd - Administration Utilities (the name of the database)
The SELECT statement includes a reserved word or an argument name that is
misspelled or missing, or the punctuation is incorrect."

I can't find what is making this error come up. I even tried turning the
warnings off prior to running the macros the run the buttons, and it still
comes up.

Any ideas how to track this?

Thanks.

Jennifer


.

Relevant Pages

  • [RFC] [PATCH] Improve list.h documentation for _rcu() primitives
    ... primitives, as suggested off-list. ... * Insert a new entry before the specified head. ... * manipulating whole lists rather than single entries, ...
    (Linux-Kernel)
  • Re: [RFC PATCH -v4 07/14] fsnotify: add in inode fsnotify markings
    ... when it hits zero and should be freed only under lock, ... and the inode->list and no other process is referencing this entry. ... freeme is set when the entry is removed from both lists. ... inode disappears (inode deleted or evicted form core, ...
    (Linux-Kernel)
  • Re: First sentence check
    ... Dim pos As Integer ... which is the insertion point when the macro is launched or the text ... what you need is a way to determine whether the paragraph ... It will show how many lists Word finds in your document. ...
    (microsoft.public.word.vba.general)
  • Re: Copy Range with Additional Rows to New Workbook
    ... Dim lastrow As Long ... set the macro to copy the range, where the last row equals the ... last row is the last entry on the sheet to copy, ... entry and keys that entry into our general ledger system. ...
    (microsoft.public.excel.programming)
  • Re: Copy Range with Additional Rows to New Workbook
    ... Dim lastrow As Long ... If we can set the macro to copy the range, ... the last row is the last entry on the sheet to copy, ... journal entry and keys that entry into our general ledger system. ...
    (microsoft.public.excel.programming)