A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Calendar Control



 
 
Thread Tools Display Modes
  #1  
Old June 16th, 2004, 07:20 PM
Ant
external usenet poster
 
Posts: n/a
Default Calendar Control

Asking about a Calendar control in my previous post on the 14/06/04, I was
advised by Stephen Lebans to:

“Dump the ActiveX control as you can get the exact same control without
the ActiveX distribution/versioning/registration issues he
http://www.lebans.com/monthcalendar.htm”



This I did and followed the very comprehensive step by step instructions in
a clean test DB. Everything worked fine and I was very impressed so
proceeded to do the same in my live application. I first did a Compile
before the import of the modules (All was fine) and then immediately after
the import of the modules. This time I got the following Compile error :
Variable not defined: dbLong



Start of code:

Public Property Let MultiSelect(ms As Boolean)

' Allo wuser to select a Range of dates instead of just one.

If ms Then

m_MultiSelect = MCS_MULTISELECT

Else

m_MultiSelect = 0

End If

' Update custom property

SetProperty "MultiSelect", dbLong, m_MultiSelect



End Property

End of Code



Being only an enthusiastic amateur and not knowing much about VB can anyone
help me out as I would really like to get this calendar control working?



PS I am using Access 2003



Thanks in anticipation



Ant



  #2  
Old June 16th, 2004, 08:42 PM
George Nicholson
external usenet poster
 
Posts: n/a
Default Calendar Control

I'm using XP but dbLong is a DAO constant, so my guess is that you need a
reference to the DAO object library. This is a very common error when
importing objects or code into a new database, since the DAO library is not
selected by default since Access 97, but is still very frequently used.

In the Visual Basic Editor: ToolsReferences: put a checkmark next to
"Microsoft DAO 3.6 Object Library" (the version number might differ)

HTH,
--
George Nicholson

Remove 'Junk' from return address.


"Ant" wrote in message
...
Asking about a Calendar control in my previous post on the 14/06/04, I was
advised by Stephen Lebans to:

"Dump the ActiveX control as you can get the exact same control without
the ActiveX distribution/versioning/registration issues he
http://www.lebans.com/monthcalendar.htm"



This I did and followed the very comprehensive step by step instructions

in
a clean test DB. Everything worked fine and I was very impressed so
proceeded to do the same in my live application. I first did a Compile
before the import of the modules (All was fine) and then immediately after
the import of the modules. This time I got the following Compile error :
Variable not defined: dbLong



Start of code:

Public Property Let MultiSelect(ms As Boolean)

' Allo wuser to select a Range of dates instead of just one.

If ms Then

m_MultiSelect = MCS_MULTISELECT

Else

m_MultiSelect = 0

End If

' Update custom property

SetProperty "MultiSelect", dbLong, m_MultiSelect



End Property

End of Code



Being only an enthusiastic amateur and not knowing much about VB can

anyone
help me out as I would really like to get this calendar control working?



PS I am using Access 2003



Thanks in anticipation



Ant





  #3  
Old June 16th, 2004, 09:53 PM
Ant
external usenet poster
 
Posts: n/a
Default Calendar Control

Thats worked just dandy!
Its easy when you know how isnt it?

Thanks

"George Nicholson" wrote in message
...
I'm using XP but dbLong is a DAO constant, so my guess is that you need a
reference to the DAO object library. This is a very common error when
importing objects or code into a new database, since the DAO library is

not
selected by default since Access 97, but is still very frequently used.

In the Visual Basic Editor: ToolsReferences: put a checkmark next to
"Microsoft DAO 3.6 Object Library" (the version number might differ)

HTH,
--
George Nicholson

Remove 'Junk' from return address.


"Ant" wrote in message
...
Asking about a Calendar control in my previous post on the 14/06/04, I

was
advised by Stephen Lebans to:

"Dump the ActiveX control as you can get the exact same control without
the ActiveX distribution/versioning/registration issues he
http://www.lebans.com/monthcalendar.htm"



This I did and followed the very comprehensive step by step instructions

in
a clean test DB. Everything worked fine and I was very impressed so
proceeded to do the same in my live application. I first did a Compile
before the import of the modules (All was fine) and then immediately

after
the import of the modules. This time I got the following Compile error

:
Variable not defined: dbLong



Start of code:

Public Property Let MultiSelect(ms As Boolean)

' Allo wuser to select a Range of dates instead of just one.

If ms Then

m_MultiSelect = MCS_MULTISELECT

Else

m_MultiSelect = 0

End If

' Update custom property

SetProperty "MultiSelect", dbLong, m_MultiSelect



End Property

End of Code



Being only an enthusiastic amateur and not knowing much about VB can

anyone
help me out as I would really like to get this calendar control working?



PS I am using Access 2003



Thanks in anticipation



Ant







  #4  
Old June 17th, 2004, 06:16 PM
George Nicholson
external usenet poster
 
Posts: n/a
Default Calendar Control

Easier, maybe. There's always something new to learn.
:-)

--
George Nicholson

Remove 'Junk' from return address.


"Ant" wrote in message
news:li3Ac.208$Fb4.33@newsfe5-win...
Thats worked just dandy!
Its easy when you know how isnt it?

Thanks

"George Nicholson" wrote in message
...
I'm using XP but dbLong is a DAO constant, so my guess is that you need

a
reference to the DAO object library. This is a very common error when
importing objects or code into a new database, since the DAO library is

not
selected by default since Access 97, but is still very frequently used.

In the Visual Basic Editor: ToolsReferences: put a checkmark next to
"Microsoft DAO 3.6 Object Library" (the version number might differ)

HTH,
--
George Nicholson

Remove 'Junk' from return address.


"Ant" wrote in message
...
Asking about a Calendar control in my previous post on the 14/06/04, I

was
advised by Stephen Lebans to:

"Dump the ActiveX control as you can get the exact same control

without
the ActiveX distribution/versioning/registration issues he
http://www.lebans.com/monthcalendar.htm"



This I did and followed the very comprehensive step by step

instructions
in
a clean test DB. Everything worked fine and I was very impressed so
proceeded to do the same in my live application. I first did a

Compile
before the import of the modules (All was fine) and then immediately

after
the import of the modules. This time I got the following Compile

error
:
Variable not defined: dbLong



Start of code:

Public Property Let MultiSelect(ms As Boolean)

' Allo wuser to select a Range of dates instead of just one.

If ms Then

m_MultiSelect = MCS_MULTISELECT

Else

m_MultiSelect = 0

End If

' Update custom property

SetProperty "MultiSelect", dbLong, m_MultiSelect



End Property

End of Code



Being only an enthusiastic amateur and not knowing much about VB can

anyone
help me out as I would really like to get this calendar control

working?



PS I am using Access 2003



Thanks in anticipation



Ant









 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 10:30 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.