Object Doesn't Support Property or Method Error

As I mentioned:

?ctl.Name
tabGInstrCertifications

that refers to a specific page of your tab control, which does indeed have "Audit" in the tag property.
 
By the way, the table with all the certifications in it isn't normalized:

http://www.r937.com/Relational.html

Sorry, I've been out sick.

What about the certifications table isn't normalized? Could you be more specific? I went to your link, but that site discusses theory, which is subject to interpretation and I need specific examples of what is wrong with my table. I suppose I could try and make changes to it, but I inherited this table and did the best I could to design a database around it.

As you can tell from viewing my db, I have numerous objects linked to the that table. Changing its structure at this point would create more problems, although I'm sure in the long run it would be beneficial. It really does work fine for what it is used for. I just need the Audit Trail code to function without an error message. Could you please help me with that? I'd really appreciate it. Thanks!
 
Don't have that VM running right now, but from memory each certification is a field, right? I would have them in a related table, where each record represented a single certification for a person. Here's the tipoff: when they implement a new certification, will your application handle it without you having to redesign tables, forms, reports, etc? A normalized db would.

It may well be too late to change it, I just wanted to point it out.
 
As I mentioned:

?ctl.Name
tabGInstrCertifications

that refers to a specific page of your tab control, which does indeed have "Audit" in the tag property.

I found that error in the Immediate Code window per your helpful advice and removed the Audit tag and still got the same error from my original post. Unless I somehow missed a field, all of the audit tags have been removed.

Don't have that VM running right now, but from memory each certification is a field, right? I would have them in a related table, where each record represented a single certification for a person. Here's the tipoff: when they implement a new certification, will your application handle it without you having to redesign tables, forms, reports, etc? A normalized db would.

It may well be too late to change it, I just wanted to point it out.
Thank you for pointing that out to me. I do understand the general idea of normalization from my college days, but for my current needs, I only require a table that lists expiration dates for various certifications. My current structure seems to satisfy that need. Here is the big picture:

Purpose: To hold information about a staff member's certification status in order to run reports and send out notifications.

Information kept for staff members:
Name
ID #'s (for tracking in different agency systems)
Job Status (active, sick leave, etc.)
Certifications (expiration dates and status [current/expired])
Notes (anything that explains something not referenced in a field)

When a new certification is implemented, my plan is to add a new field to the table. I would then need to add a new update query, report and redesign the form that contains the listing of all certifications.

I'm not sure I understand how a normalized db would prevent me from needing to add new queries, reports and redesigning forms when a new certification is implemented. Perhaps you could elaborate when you get a chance?

I am open to making changes, but I am also working under time constraints. Thanks again!
 
Regarding the error, you removed the tag from that page (not the tab control, but the page within the tab control)? As I recall it ran without error for me once I cleared that.

In a normalized db, I'd have a table for the various certifications, along with a form to allow the users to maintain the list. When there was a new certification, the users could add it there. That table would be the source of combos or listboxes where the users would choose the appropriate certification(s); those would update automatically to show the new addition. Since you'd have a one-to-many relationship between people and their certifications, you'd be using subforms/subreports, which would also grow dynamically. Like I said, as a developer I wouldn't even know they had added a new certification.

If you had a product sales db, would you have a field for each product (please say no)? This is no different.

Again, it may be too late for you to change this, I was just trying to educate.
 
I should have added that your existing table would not have any of the certification fields in it. You'd have a related table with 3 fields: the staff ID field from your table, the certification and the date.
 
Regarding the error, you removed the tag from that page (not the tab control, but the page within the tab control)? As I recall it ran without error for me once I cleared that.

In a normalized db, I'd have a table for the various certifications, along with a form to allow the users to maintain the list. When there was a new certification, the users could add it there. That table would be the source of combos or listboxes where the users would choose the appropriate certification(s); those would update automatically to show the new addition. Since you'd have a one-to-many relationship between people and their certifications, you'd be using subforms/subreports, which would also grow dynamically. Like I said, as a developer I wouldn't even know they had added a new certification.

If you had a product sales db, would you have a field for each product (please say no)? This is no different.

Again, it may be too late for you to change this, I was just trying to educate.

When you ran the code (Audit Trail) did it track the changes you made in fields that were not tagged? I ask because the instructions included with the code indicated that I must tag the fields I want to track, otherwise the software is useless.
 
I don't recall, as I was focused on the error, and that VM isn't running. You do need to tag the fields (more correctly the controls containing the fields) for the code to work. The point is, you had the tag on something other than one of those controls, and something that doesn't have a Value or OldValue property, hence the error. In this case, you want the tag on the text boxes, combo boxes, etc on that page of the tab control, but not on the tab control or any of its pages.
 
@pbaldy,

Everything is working fine now. I found the place on the tab control where the Audit tag was inadvertently listed and removed it. Apparently, tab controls have several clickable areas and I overlooked one of these when removing unnecessary "Audit" tags.

Thanks again!
 
Happy to help! Yes, there are a lot of options in that area.
 

Users who are viewing this thread

Back
Top Bottom