Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / ActiveX Controls / March 2005

Tip: Looking for answers? Try searching our database.

mscomct2.ocx

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ReidarT - 23 Mar 2005 09:34 GMT
Is it possible that different versions of the Windows common control can
cause problems
in a network-environment?
regards
reidarT
Scott McDaniel - 23 Mar 2005 14:09 GMT
Different versions of any .ocx or .dll can cause problems if you've used
version-specific features in your application. For example, if your code
uses a feature available in Version 7.1.02 and the user only has version
6.5.00, then your code will fail.

To avoid these items, make sure that you develop to the "lowest common
denominator" and that you throughly test your application on a machine that
has the minimum requirements installed. For example, if you intend to only
support version 7.1.02 of MyCoolStuff.dll, then make sure your test
environment includes that file (and not later versions). Then, when
installing your application, check to ensure that your users have this
version (or a later one, assuming compatibility between versions) ... if
they dont' have the minimum required version of MyCoolStuff.dll, then inform
them of this and take appropriate action (abort the install, install the new
DLL, whatever is best in your scenario).

> Is it possible that different versions of the Windows common control can
> cause problems
> in a network-environment?
> regards
> reidarT
John Webb - 23 Mar 2005 18:54 GMT
Yes, what he said.

you specifically mention the common control library - I first encountered
problems with this when I was developing a database on a machine that had
service pack 2 installed (Windows XP), and found that the library was
updated in this service pack - at least that is what I think.

So definitely follow Scotts advice, and always prepare for the lowest
common denominator.  Testing is a must in a networked environment, if
possible you should always test on each platform the application will be
used on.  Further to that, I would outline the platforms the application
has been tested on to your client, and advise them that if they plan to let
anybody further access it, you will need to test it on their setups first.

Cheers

John Webb
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.