By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,188 Members | 834 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,188 IT Pros & Developers. It's quick & easy.

Licensing question

P: n/a
Hello. I created an application using visual basic with an Access database. My family wants to use the application on their computers, but they don't have Access on their pcs. If I copy the mdb file to their pc without them having Access on their pc, am I violating any licensing agreements? Is there a fee for this? If so, where do I go to pay the fee? I don't want to get anyone in trouble, so I figured I'd ask first. If someone could let me know I'd appreciate it. thanks.
Nov 22 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
emg
One variation that works under Visual Studio 6 might also work under VS.Net
.. . .

If your VB application just reads and writes data to an Access database, but
your users never need to fire up the Access GUI to run reports or forms
within Access, you don't even need the Access developer license. Your vb
code can open a connection to the database, read/write, close connection and
you're fine.

The problem comes when you want to run an Access Report, display an Access
Form or do other GUI-related things. Then, as Jayson said, you need the
Access developer edition in order to have the distributable components
necessary for deployment. But if your VB program does all the GUI work,
you're fine.
"Jayson" <ja********@carolina.rr.com.NO_SPAM> wrote in message
news:04**********************************@microsof t.com...
you will need to package up your access application by using the developer edition of office. basically, it will just install the runtime version of
access on their machines. i don't know the licensing specifics, but i
believe you can distribute it freely then.
hth
jayson

Nov 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.