 |
|
|
|
Topic: MS-Access 2003
|
| By: Guest | Posted on: Oct 1 2012 at 09:27:15 PM | | Need to add serial communication with an MS-Access 2003 application 32-bit. Users run this front end on Win7 64-bit and Win7 32-bit work stations. Which component should I use? | |
| By: Guest | Posted on: Oct 2 2012 at 10:00:15 AM | You ask "which component" so I assume you're wondering whether to use sComm32.OCX or Comm64.DLL
Comm64 is a .net component. MSAccess won't use .net components so that answers your question. The only one that will work with MSAccess is sComm32.OCX
But there's a problem. The licensing of SComm32 means that anyone who uses it in an IDE (ie in a development environment) must have a developer license. When running on the user's computer MSAccess MDB always looks like an IDE so the Comm OCX will think it's running in an IDE and will expect the user to have a developer license.
So, by all means, use sComm32 but spend some time looking at how you will deploy your system to your users and make sure you can deploy as you expect.
The best method is to build the data/Comm32 code into a vb6 exe and then you'll have no problem deploying the OCX to all users. | |
|
