I changed the actual calendar form to Modal, run in Top Level Form --
which is what I need.
That's when I got the bugbox described below.
It's just not worth my wasting any more time over it. They'll just have
to type their dates like the rest of the world... :-)
Richard Kaye wrote:
In your original post, I thought you said you had a textbox with a
down arrow to display a calendar that you wanted to replace. That's
pretty much what the caldatepicker class is. Try using that instead of
the calendar form class. Having said that, did you try
oCalendar.Show(1)? That should show the form modal.
Chet Gardiner wrote:
Among the problems I'm having with this little object is that the
calendar is a modeless form. It flashes and doesn't stay on the screen.
I tried changing it to a modal form that displays in the top level
form (which MUST be the case in my application), I changed the click
event from READ EVENTS to oCalendar.show(), it shows but it still
craps out on me bugbox = "oCalendar is not an object" after I pick a
date. It also won't ESCAPE without forcing you to pick a date.
Not acceptable, alas!
ENOUGH, ENOUGH, ENOUGH, Already!!!! Unfortunately, I've got WAY
too many hours into this goddamn project as it is (MY LAST project as
a programmer for hire!!!). The more time I spend, the more it costs
ME (fixed price DAMN IT).
I'm going to change them all to plain text fields and to hell with it!!!
C
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
