2010 f@#$@#$@!

[CHAOSinACT]

they removed the calendar control and snapshot viewer from 2010 access. both are problems for me....yuck!!!

i know snapshot def gone, anyone figured a way to reference and get the calendar back yet?

 

[Banana]

Why would you care?

You now have calendar built-in so that's actually one less reference hassle to deal with. Just set Date Picker property accordingly.

As for snapshot... you now have PDF export built-in and PDF is much more universal than the .snp format was so use it.

It's inconvenient to us as developers but this is very good thing for users, IMHO.

 

[CHAOSinACT]

Why would you care?

You now have calendar built-in so that's actually one less reference hassle to deal with. Just set Date Picker property accordingly.

As for snapshot... you now have PDF export built-in and PDF is much more universal than the .snp format was so use it.

It's inconvenient to us as developers but this is very good thing for users, IMHO.

except i'm meant to deliver asap and they upgraded the office without telling me. i know i can write around it but far prefer to deliver and then get a new version to them asap. i get datepicker -but the calendar control seemed unlikely to go and gave a great visual reference to before and after dates. ok, moving to pdf might help users (though we had snapshot viewer working already so not really here), but i fail to see why remove the calendar control. still what MS does we cannot just undo i guess.

 

[Banana]

Well, FWIW, whenever I hear about 'calendar control', it's usually in scorn rather than praise and indeed if one googles a bit, some Access developers basically encourage shunning it although and using API calls instead to avoid the inherent problems in calendar control. Many developer likewise try to avoid using ActiveX controls for similar reasons.

I'm sorry that you're in this unfortunate situation but I honestly can't see how this is not a good thing that Access now has a native calendar control built-in, thus freeing you & me & any other developers of the usual headaches that comes with the litany of solutions/workarounds we dealt with the old calendar controls or API calls.

I think the main reason is that Microsoft wants to move away from COM and ActiveX technology - in fact, there will be no 64-bit version of calendar version or treeview control or other controls that comes in the comctl.ocx. So while Access is definitely moving ahead into 64-bit world, it'd be better off to do without technology that are no longer blessed by Microsoft.

 

[CHAOSinACT]

are you saying microsoft is phasing out active-x altogether? i hadn't heard that. not sure what u mean by lack of 64-bit versions as i'm on windows7 64bit and calendar control always worked. but your right; getting rid of it didn't kill me. i wasn't really using them for date selection *though u could* i used them to visual display dates - i thought it was nice. actually the snapshot viewer bugged me more from a reworking pov but your right in the long run PDF is better.

 

[Banana]

That's my speculation. I don't think Microsoft has given an official announcement, but to me the writing is on the wall. .NET is the future, (some might say the present).

As for working on 64bit Windows... did it work in a 64-bit application? Note that you can run 32-bit application on 64-bit Windows, and in that case, would work just fine. It's when you need to run 64-bit application when it no longer is available.