Forms Collection Quit on me - Access Developer Forum


	Back to Access Developer Forum Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

Forms Collection Quit on me

Robert Fivey

4 years ago

I have create a wonderful CRM DB for my wife thanks to this site. I am truly thankful!

I have a version running now that is currently working as designed. Below is a small sample of my code that pushes some info to the Timesheet form. It works in my current release.

Forms![Timesheet_F]!CustomerID = Me.CustomerID
Forms("Timesheet_F")!TimeAccruedBy = TempVars("EmployeeID")
Forms("Timesheet_F")!Description = "Bookkeeping"

However, as I am always trying to add new abilities to my now very excited CEO, My current build has made every one of my Forms collection references error out with an: "Object doesn't not support this property or method."
These all currently work, but something I added, changed but for the life of me can't find what it is. Only changes have been to subform linking, buttons to run a shell command to bring up a file explorer, and clean up some odds and ends. No changes have been made to the majority of the pages that have vba using the Forms collection that are now erroring out.
Are there any ways to enable/disable forms functionality through vba? Just very confused on how forms collection that is working on one build does not work in another....

Help me Obi-Wan!! Your my only hope!

	Alex Hedley @Reply 4 years ago
Compile

	Alex Hedley @Reply 4 years ago
Troubleshooter

	Kevin Yip @Reply 4 years ago
When the error occurs, click "Debug," and see which line, or portion of a line of code is highlighted in yellow. I'm guessing it's "Me.CustomerID" because that's the only "property or method" I see. All the other lines use "!", which would've given a different error.

Richard Rost @Reply

4 years ago

First thing I would recommend is getting rid of non-alphanumeric characters from your object names. You're referencing them correctly with the [brackets] but I still hate them. Also, you really don't need the Me. in front of CustomerID if it's on the form where the code is. Shouldn't hurt, but it's unnecessary. USUALLY that's reserved for properties like Me.Caption. And yeah, I'd try to maintain some consistency with your nomenclature. But like Kevin said, hit the Debug and send us some screen shots. There's nothing technically wrong with what you've posted. I'd need to see it.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Developer Forum.

Next Unseen

New Feature: Comment Live View