DataBase - Access runtime automation
Asked By Loterken
19-Mar-10 04:59 PM
if only access runtime is installed (not office)
can access runtime be used as an automation server ?
if so, with late and early binding
tia
SQL Server
(1)
PleaseNOOSpamKallal
(1)
Database
(1)
CreateObject
(1)
DougSteele
(1)
GetObject
(1)
Edmonton
(1)
Windows
(1)
Douglas J. Steele replied to Loterken
To the best of my knowledge, yes.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
Sylvain Lafontaine replied to Loterken
You cannot use CreateObject to create an Access application from the runtime
but you can use a Shell comand to open one and then use the GetObject
function to get a reference to that instance. See the following article for
more details:
http://support.microsoft.com/kb/145707
For early binding, I do not know but as they are many different versions of
Access, my first reflex would be to use exclusively late binding.
--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Blog/web site: http://coding-paparazzi.sylvainlafontaine.com
Independent consultant and remote programming for Access and SQL-Server
(French)
Albert D. Kallal replied to Loterken

As Sylvain points out, you sort of can.
The problem is if you create an instance of the access runtime, because you
cannot supply the file name to open when you do this, the runtime actually
shuts down by itself.
However what you can do is shell out and launch a copy of the runtime using
shell. When you do this, then you can provide the access database files open
as a parameter in that shell command.
Once the addition of Access is launched and running, then you can use get
object in your code.
So you are free to use late binding, and in fact I think even early might
work, but you cannot use create object, you have to use get object to get a
running instance of access.
So the only change or limitation is that you have to have Access running and
launched before you attempt automate access runtime.
The above limitation does not exist for the full Eddition of Access, but as
the KB article linked to shows you can well work around this limitation.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com

SQL query slow DataBase Hi In the code below I found that it takes 1.3 seconds to load to split it up or cancel the query? And can I read this faster? string sql = EquipmentID(Equipment) + StartDate.ToOADate().ToString(FloatFormat, myCulture) + EndDate.ToOADate().ToString(FloatFormat, myCulture); sql + = " group by event_id, name"; _Log("Calc thread #2"); OleDbCommand com = new OleDbCommand(sql, con); _Log("Calc thread #3"); From #2 to #3 it takes 1.3 seconds. Remaing less that 0.1 second. So the query is what slows it down. Access Discussions SQL Server (1) Linson Unlike Albert D. Kallal (1) MySQL (1) Windows Server 2003 (1) Visual Studio (1) SharePoint (1) NHibernate (1) Microsoft SQL Server (1) Hi, Besides
Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed reading this article, is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will 2010 does not really save them money (because of the 64-bit requirements of Sharepoint Server 2010, it could vastly increase those costs for organizations with legacy hardware). The features of email hosted by someone else, so it is not a paradigmatic change. Having your flagship database applications hosted outside your local LAN seems to me to be a big leap, and http: / / www.dfenton.com / contact via website only http: / / www.dfenton.com / DFA / Access Discussions SQL Express (1) SQL Server (1) MySQL (1) Exchange Server (1) Windows Server (1) SharePoint (1) David W. Fenton (1) Access 2010 (1) Everything you
Using Mysql or SQL server as backend to Access front end DataBase Have a client having problems with a fairly complex Access system which is split into end. Using access 2003 / mdb format with Access 2007 software. We are surmising that recent server problems or connectivity problems may be to blame. If we converted to MySQL or SQL server as the back end, would that eliminate the potential for Database corruption that can occur with Access Jet databases when you lose connectivity, when someone shuts down their PC with the database active, etc? If so am I correct that you connect via ODBC rather than using
Cannot link to SQL server DataBase Can any of you guys help? I am new to using SQL Server. I have a database that I wish to upsize from Access to put the back end on a server, and use Access as a front-end. However, I am stuck at the very first stage - I cannot link Access to the SQL server. I am using SQL Server Management Studio on a single computer for development purposes
Aaron Kempf's MCITP DBA proof DataBase https: / / mcp.microsoft.com / authenticate / validatemcp.aspx transcript: 944364 AccessCode: helloworld Access Discussions SQL Server 2008 R2 (1) SQL Server 2008 (1) SQL Server 2005 (1) Microsoft SQL Server Reporting Services (1) Regards Larry Linson Microsoft Office Access (1) Bing Microsoft SQL Server