Calendar icon in Access 07 & higher

FuzMic

DataBase Tinker
Local time
Today, 21:55
Joined
Sep 13, 2006
Messages
744
Hi guys/gals

As some of us is sticking to Access 03 & lower, the calendar icon that Access 07 display next to a date field in a form, is sometimes unwanted ie running Access.03 .mde from RunTime 07. Do anyone of you know how to turn it off from Access 03?
 
On each date textbox, set the Show Date Picker property (in the Format tab) to Never.
 
Thanks Inet

Does it mean i have do it in Access 07+ as Access 03 do not have this property in the Format tab. Assuming I do it Access 07, then what happens if the .mde is made in Access 03- ?
 
Yep, you will need to make the change to the mdb in Access 2007+, save and close your db. Then go back to Access 2003 and make your mde. It should retain the settings when you later open it in 2007 runtime.

You can also do it in Access 2003 through code and pre-conditions (because the code will fail if you don't) but this is too much work.
 
Thanks again

I would like to see how to do it codes & its precondition in Access 03.
 
what happens if the .mde is made in Access 03- ?

You mentioned in your OP that you are running the app with Runtime07. Why keep going back to 03? Just keep developing in 07 and distributing the app as accdr or accde.

The Package Solution Wizard can bundle up Runtime07 with the accdr, in the installer, for easy distribution.
 
You mentioned in your OP that you are running the app with Runtime07. Why keep going back to 03? Just keep developing in 07 and distributing the app as accdr or accde.

The Package Solution Wizard can bundle up Runtime07 with the accdr, in the installer, for easy distribution.
Are you sure you can make a accde or accdr from an mdb? ;)
 
Not directly.

First save the .mdb as accdb
Once its an accdb you can make it an accde
Package Solution (Developer) will make the accde an accdr if you want it to and bundle it up in an .msi installer file along with Runtime (if you want it to). Or there is an option for the person downloading and installing Runtime if 07 is not installed. This adds about 45mb to the file.

Personally I have an absolute loathing for people who distribute software that then needs to download more software before you can use it. I would rather download a 50mb file and have everything than download a 5mb file and then be told, at the end of the install, that another 45mb file needs to be downloaded. The price we pay for living in deepest darkest Africa. No dsl or cable.

Use 03 if you are more comfortable using it.
Use 07 or 10 if you are more comfortable using it.
 
A complete migration then. There would be lots of contingency plans in place before considering migrating. For example, the main thing is security. If FuzMic is using the workgroup file for managing users then he/she will lose that functionality.
 
Thanks mates for the exchange relating to why stick to Access03-. Essentially i feel more comfortable with a .mdb or .mde for front end and the Access07 runtime is free for all users without Office Prof & backward compatible. There are too many objects in the architecture to test out.

On the point of having to download more things: In anyway we need latest version of .net framework, sp# for windows and whole lot to download for any new programs to work. So download a additional runtime is no issue really.

However if user don't have any connection, then the developer has to go on site or send them a CD with all the downloads. So i still think download & living with many new objects in this fast changing environment, is no issue for me, at least.

Inet, your help works: going forward, set the to "never" on date fields, then go backwards the .mdb removes the popup calender. I presume it will work with the .mde from it from Access03-.
Still hoping to do it by codes.:)

Cheers!
 
Inet, your help works: going forward, set the to "never" on date fields, then go backwards the .mdb removes the popup calender. I presume it will work with the .mde from it from Access03-.
Still hoping to do it by codes.:)

Cheers!
Glad to know!

If you want to know more about pre compiling you can Google the term #If...Then...#Else Directive

E.g., in the Declaration section:
Code:
Option Compare Database
Option Explicit

Const IsPostAccess2003 As Boolean = [COLOR=Red]True[/COLOR]

In Open event of form:
Code:
[COLOR=Red]#[/COLOR]If IsPostAccess2003 Then
    Dim ctl As Control

    For Each ctl in Me.Controls
        Select Case ctl.ControlType
            If ctl.ControlType = acTextbox Then
                Me.ShowDatePicker = 0
            End If
        End Select
    End If
[COLOR=Red]#[/COLOR]End If
Notice the "#" surrounding the If and End If lines? Anything within those that block of code will not be seen by the compiler so it won't complain when you write Access 2007 code in an Access 2003 mdb and package it.

But you will have to set the Const variable above before packaging.

See what I mean? Not worth the effort.
 
Inet, Thanks for NEW insight & NEW toy, will play with it. Cheers!!
 

Users who are viewing this thread

Back
Top Bottom