Access RunTime
CTY
application if only the runtime is installed on a computer. I tried it and
it doesn't work. But is there a way to work around it, or is it by
design(i.e. requires every user to buy a full access license.)??
Thanks...
--
Frank Miller [MS]
My name is Frank Miller. Thank you for using the Microsoft Access
Newsgroups.
As I understand your question, you want to know if VB .NET can work with a
Run-Time Access application.
I can answer your question in part as I am not a VB .NET support
professional.
When an Access run-time application is installed, we install exactly the
same JET database engine that is used when the database is running in full
Access. This means that any outside use of the database is identical
regardless of whether full or run-time Access is installed on the machine.
When Access is removed from the machine, the JET Engine is not removed as
it is frequently used by applications other than Access.
If your VB .NET code is capable of working with the Access MDB file, it
shouldn't matter if full Access, run-time Access, or no Access at all is
installed on the target machine. It only matters if the appropriate JET
Engine and MDB file is installed correctly.
I hope this helps! If you have additional questions on this topic, please
reply to this posting.
Regards, Frank Miller
Microsoft Support
This posting is provided “AS IS” with no warranties, and confers no rights.
Peer-to-peer newsgroups are available to help you interact with other users
of our products including Microsoft " Most Valuable Professionals" - MVP's.
For more information please see
http://communities.microsoft.com/newsgroups/default.asp?icp=GSS&slcid=us
Tony Toews
>Is it possible to use VB.Net code to programmatically work with an Access
>application if only the runtime is installed on a computer. I tried it and
>it doesn't work. But is there a way to work around it, or is it by
>design(i.e. requires every user to buy a full access license.)??
What do you mean by "work with an Access app"? If you mean link to
tables and such then I'm sure that can be done in ADO. If you mean
using Automation to run forms and reports then they must either
install the full version of Access or a runtime version of Access.
See the Office Developers Edition or whatever its called at
microsoft.com/office.
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
CTY
automation to open a report or customize a query, the vb code give errors.
I was wondering if this is a limitation of the runtime and if there was a
workaround.
Thanks...
"Tony Toews" <tto...@telusplanet.net> wrote in message
news:6davbukukbdh0ertc...@4ax.com...
Frank Miller [MS]
Tony brings up an excellent point and there *is* a way to automate a
Runtime version of Access but it is not obvious.
When the user installs the Access application on a machine that does not
have the retail version of Access, a Runtime version of Access is
installed. The Access Runtime installs and registers similar to the retail
version and the executable is also called msaccess.exe. The Access Runtime
allows an Access application to run on a client machine, but the Access
Runtime does not allow you to develop new applications or modify the design
of existing applications. One of the requirements of using the Access
Runtime is that it must be started with a database. Because of this
requirement, if you want to automate the Access Runtime you must launch the
msaccess.exe and specify a database to open, then use GetObject to retrieve
the Application object. Then you can proceed with automating the Access
Runtime. If you attempt to automate the Access Runtime with the New keyword
or with CreateObject, you will receive an error such as the following when
trying to instantiate the instance:
-2147023186 The object universal unique identifier (UUID) was not found.
The following article identifies the issue:
Q295179 - ACC2002: Can't Use OLE Automation with Access Runtime
http://support.microsoft.com/support/kb/articles/q295/1/79.asp
However, this article doesn't identify a workaround. The workaround is to
Shell to Access and provide the database name and any other needed
parameters such as the /runtime switch, user, and passwords.
The VB .Net group is currently in the process of writing an article that
will describe how to perform common functions such as printing custom
reports, modifying secured database files, and manipulate controls on forms
in Access from VB .Net.
You may want to check periodically for the following article to become
available.
Q317113 - HOW TO: Automate Microsoft Access From Visual Basic .NET
This article will be quite lengthy but it will provide a wealth of
information on this topic and should include a good deal of sample VB .Net
automation code.
CTY
"Frank Miller [MS]" <Frank-NoS...@microsoft.com> wrote in message
news:Qgr#yCj6BHA.1888@cpmsftngxa08...