Networked Date Errors 1

[jameshall]

Hello,

I have been in the process of updating a version of a timelogger for my department. It has started to be used, on every PC. The front end has been installed, each PC has been generating different errors.
Most have been solved but two remain
1) The references in VB editor keep changing depending on the installation of Access, is there simple way solve this without doing it manually?
2) The annoying error is the ActiveX date and time picker, this has given me problems throughout development. On every PC it gives a different error from not licensed, not appearing on the screen, by being locked and providing the date in a different format (giving mismatch errors when manipulated). Is there another way to do this so I can get rid it.
I am fairly new to Access (4 months)

Any help would be appricated on this as it holding up other work
Thanks in advance

R.I.P DTPicker

 

[oharab]

James,
Which references are missing? By default there should be 4:
Visual Basic For Applications
Microsoft Access 9 Object Library (assuming A2k)
OLE Automation
Microsoft ActiveX Data Objects 2.5 or Microsoft DAO 3.x


These should be installed whatever the installation. Any others, eg word/excel/etc can be ignored and Late Binding can be used instead.
ie instead of dim xl as New Excel.Application
you would use
dim XL as Object
set xl=createobject("Excel.ApplicatioN&quot

The date picker is a funny beast that is best avoided in my opinion. Have a look at

http://www.lebans.com/monthcalendar.htm

for a much better date picker that will solve all of your problems.

HTH

Ben
----------------------------------------
Ben O'Hara

http://www.RobotParade.co.uk

----------------------------------------

 

[jameshall]

Brillant!!

The time picker is history, Thanks
With the references I (long way) got a test PC and installed a standard verison of Access, Fixed any errors from testing. Then I made it in to a MDE file. This appears to have fixed the problems on most installations at this time.
I assume that the MDE file locks things like this!!

The references used are the 4 you said including
Microsoft VBA Extensibility 5.3
With the PCs with the errors I did not record what they were but they were different to this

Thanks again

Jameshall

 

[oharab]

Do you need the Microsoft VBA Extensibility 5.3?
If not, then I suggest you get rid of it in your development file, create an MDE from that and distribute it to your users.

Good luck!

Ben ----------------------------------------
Ben O'Hara

http://www.RobotParade.co.uk

----------------------------------------

 

[jameshall]

Hello Ben

I am not quite sure what the 5.3 library does. Have you had any experiences with it?

Regards

James

 

[oharab]

AIIRC I've never used it. From what I can tell it includes objects for manipulating the VB Editor, but I'm not sure. I would suggest that if you are not creating/changing VBA modules on the fly, then you don't need the library.


Cheers

Ben ----------------------------------------
Ben O'Hara

http://www.RobotParade.co.uk

----------------------------------------