Calendar works on first entry, but not when user enters another task
I am using Steven Lebans Calendar function adn it works perfectly for the first entry. This is on an unbound form but the problem is if the user wants to enter more than one task, one the second task, when they hit the calendar text box, an error message of Run-Time 13, Type Mistach comes up. How can I re-use the form witout having to close and reopen when there is more than one entry to be made?
ASKER
Will have to do this on Monday when I get to work. Wat a task is, say a developer is given a project to create an Access 2003 database that tracks documents. Tasks are what the developer will need to do to gather user information, needs, requirements, etc. So, tasks could be meet with end users, create data map, prototype code - three tasks related to one project and each task could have different due dates. I would like the developer to be able to put these three separate tasks in without having to close the Task Entry form and reopen to enter the next task. Right now, after the task is saved, there is code to reset all fields to empty text strings so I think it has something to do with properly re-setting the text control the calendar is attached to, it needs to be reinitlalized and I am not sure how to do it. So, sample db on Monday!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Simply needed to tell the system to re-iniitalize the calendar class.
So when you say "Task" you must provide context for this.
Remember we know nothing about your applications, so it is difficult to make any suggestions.
Can you post a sample db, or at the very least, the code involved?
Sample database notes:
1. Back up your database(s).
2. Combine the front and back ends into one database file.
3. Remove any startup options, unless they are relevant to the issue.
4. Remove any records unless they are relevant to the issue.
5. Delete any objects that do not relate directly to the issue.
6. Remove any references to any "linked" files (files outside of the database, Images, OLE Files, ...etc)
7. Remove any references to any third party Active-x Controls (unless they are relevant to the issue)
8. Remove, obfuscate, encrypt, or otherwise disguise, any sensitive data.
9. Compile the code. (From the VBA code window, click: Debug-->Compile)
10. Run the compact/Repair utility.
11. Remove any Passwords and/or security.
12. If a form is involved in the issue, set the Modal and Popup properties to: No
(Again, unless these properties are associated with the issue)
13. Post the explicit steps to replicate the issue.
14. Test the database before posting.
In other words, ...post a database that we can easily open and immediately see and/or troubleshoot the issue.
And if applicable, also include a clear graphical representation of the *Exact* results you are expecting, based on the sample data.
JeffCoachman