.dll versus .ocx

  • Thread starter Thread starter DS
  • Start date Start date
D

DS

I have an Access database for processing credit cards. There is a choice of
using .com(.dll) or Control (.ocx). Is here an upside or a downside in
using one or another? Is one more stable? Is one more vanilla than the
other? Also to take it a step further will Winhttp replace any of these?
Is Winhttp stable? Any Suggestions or comments welcomed. Thanks.
DS
 
DS said:
I have an Access database for processing credit cards. There is a choice of
using .com(.dll) or Control (.ocx). Is here an upside or a downside in
using one or another? Is one more stable? Is one more vanilla than the
other? Also to take it a step further will Winhttp replace any of these?
Is Winhttp stable?
Click to expand...

Use DLLs if they work just by being installed in your front end
applications folder. (Such as "C:\Documents and
Settings\ttoews\Application Data\<your app name>"

OCXs require registering which means admin rights. If the DLL works
in your app folder it doesn't require registering and can be updated
any time by you.

This is exactly how Lebans PDF printing DLLs work and it's terribly
convenient.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Back
Top