--------------------
Jeff Conrad - Access Junkie - MVP Alumni
SDET - XAS Services - Microsoft Corporation
Co-author - Microsoft Office Access 2007 Inside Out
Presenter - Microsoft Access 2007 Essentials
http://www.accessmvp.com/JConrad/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com
----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.mspx
----------
I installed Office Enterprise 2007. Then I installed DEveloper Exrtensions, then Access Runtime 2007. All appear to have installed OK - they appear in Program and Features. Instructions on runtime packaging tell me that a Developer option should appear in the resulting drop-down when I click the Office button (top-left round thing) when I have a d/b open in Access. It's not there! I have un-installed and re-installed the extensions and the runtime - still nothing! Help! I do have Runtime 2002 (XP) on the same PC, is that relevant?
According to Clint Covington, Microsoft intends to release the runtime and developer extensions for free.
My opinion is that it should ALWAYS have been free instead of slapping us Access developers with an extra cost so our users don't need to pay hundreds of dollars more to use our applications. I can't think of ANY other development environment that has this drawback.
I have installed Microsoft Access 2003 and Microsoft Access 2003 Developer Extensions. I can create Access application by using the Package Wizard. But after I upgrade from Microsoft Access 2003 to Microsoft Access 2007. I can't use the Package Wizard.
How in the world do I add a trusted location with only the Runtime version of Access 2007 installed on the PC?
I am in the process of distributing some new runtime-only applications; how do I stop the irritating "potential security risk" warning from coming up everytime the user logs in??? I can't figure out how to get to the "trust center" with only Access Runtime installed. Users don't have any other 2007 applications like Word or Excel either, and are running Windows XP, NOT Vista.
I am having a problem running Access 2007 runtime on a workstation. I have set up the 2007 database (.accdb) on our server and am able to connect to it and open it from the pc that has Access 2007 full version installed and it works fine.
I also installed Access 2007 runtime on another PC and was able to open the database using the runtime version just fine.
However, on this other PC, I installed the runtime version, and when I use the command line (msaccess.exe /runtime \serverdirectorydatabase.accdb) to open the database in runtime mode, Access opens for a split second and then closes immediately.
When I just run msaccess.exe, it opens the runtime version and says that I have not specified a database, as expected. So, I am wondering why it is not opening the database when i DO specifiy the database.
If i specify an incorrect directory for the database, it opens the runtime version and a dialog appears telling me that a database was not found, and upon clicking OK, the program closes.
I can say, that when I run it off the computer that works through the runtime version, I get a security warning telling me that there are potentially unsafe elements in the database, but i just have to click OPEN and it still opens it fine.
Perhaps the non-working PC is denying it access due to these security issues?
I can't seem to figure this out, and any help is appreciated.
I am making my very first tentative steps to convert my most complex Access 2003 app to run under Access 2007. There are no obvious problems when simply opening my original MDB file in Access 2007 or running it after conversion to an ACCDB file. However, when I try to run the ACCDB file under the Access 2007 Runtime I get a "You can't carry out this action at the present time..." error. This is then followed by the "Execution of this application has stopped due to a runtime error..."
To be more specific, I only get that error when I deliberately hide the back end database and thus invoke code triggered via Autoexec to allow the user to browse for the missing database. This code works fine when running under normal Access 2007 so it appears to be a Runtime issue.
I have setup a small application with front/back end in local network. On client machines i have installed access runtime. Although it works fine but it suddenly quit when there is any run time error while working on client machine. Although on server machine ( where full version is running it didn't close the application ).
What i need is an option to not quit the application completely. As i am not expert in coding of try/catch statements I need a simple solution for time being .
I was hoping all the errors had been addressed in the current Runtime release..... But no. If you have a previous version of Access ...2002 for example... And load the 2007 Runtime, your applications developed in 2002 will run fine in 2007 runtime. BUT.... If you open them in 2002 you receive many errors. "onClick" errors that don't exist. So if you do not have the full version of 2007 on the computer you would need to uninstall the runtime to be able to make any changes in your app.In short.... your going to screw up anyones ability to work with a previous version if you install 2007 runtime.I will try this on another computer with Access 2003 to see if it gives the same errors after runtime install. I'll post results.OK.... After trying the Runtime on another computer with Access 2003 it appears to be OK. The problem still persist with Access XP (2002). They simply do not play well together. I guess Microsoft did not feel this was important enough of a problem to address. So, if you load a Runtime of 2007 on a machine running Access 2002 you will no longer be able to use 2002.
I have packaged a 2007 db on a 2003 server. The db contains autoexec macro which: a. opens a query, b. opens a form with cmd button that returns a msgbox c. Runcode a function that calls a subroutine to return a msgbox.
Everything runs fine on server since that's where the real 2007 install is.
On my pc I have xp2 and one install of access 97( don't ask) along with office 2003 installs(excel etc, etc).
I installed access 2007 runtime on my pc.
I copied the package from the server to my pc and did install. When db finally opens the query runs, the form opens but fails on the runcode. The code behind the cmd button returns nothing. This tells me that on vb was included with the db when it was packaged or I don't have rights to run it? Either why how can I resolve this issue as info on subject is nill.
On trying to import an Excel 2007 file into Access 2007 I get the following:
1) Choose "External Data," Import, Exce 2) Select small file in MS Excel 2007 format. 3) Click on Import the source data into a new table ... 4) Choose OK
Immediately get "Microsoft Office Access has stopped working. Windows is checking for a solution to the problem..." This message never resolves, so I have to click 'Cancel'.
Then I get "Microsoft Office Access is trying to recover your information..." I have to click "Cancel" here as well and then kill MS Access in Task Manager.
Event Viewer gives following message, which is of no help: "ID: 2, Application Name: Microsoft Office Access, Application Version: 12.0.6211.1000, Microsoft Office Version: 12.0.6215.1000. This session lasted 710 seconds with 120 seconds of active time. This session ended with a crash."
Trying to import a small Excel 2003 file leads the same result. The same happens with a CSV file.
I have uninstalled and reinstalled Office 2007 as well. I am using Vista Ultimate.
Just a reminder that US Daylight Savings Time ends 4 Nov 2007 (First Sunday in November) at 0200, at which point the time (minus Indiana) reverts to 0100.
If getting your PC to cooperate is a problem, you might check the following for guidance: http://www.uic.edu/depts/accc/systems/daylight/windows.html
Hi, In Access 2007, I don't seem to be able to scan through a few records by holding down the advance record arrow in tables liked I used to?! Am I missing something here, it worked in the same way in all other versions, the same as if you use the mouse wheel, it should run through each record in turn.
Is there a way to change this? I've been through all the settings I can think of...
We have two computers in a work group. On computer1 I have the back-end and front-end database files in the shared folder and 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the error message "Microsoft Access can't Find The Database 'C:Documents and SettingsAll UsersDocumentsdb.mdb' Make sure you entered the correct path and filename" On computer2 I have the front-end database files in the shared folder and pointing to the same back-end database on computer1. Again 2 users out of 4 can access the database no problem. When the other users try to access the database they receive the same error described above.
I expect that this is some sort of windows permissions issue? There are some clues to this fact .. The two users that can't access the database are limited accounts, but I tried making them administrators and this had no affect. Their shared documents folder does not have a hand underneath it?
Any help on this appreciated as it's really starting to annoy me now!
I have access 2003 installed, which I use to make systems ( doh )
Anyway, I have just installed Access Runtime on the same machine so that I can test my databases on the runtime version to make sure that all works ok. However, I have installed several times now, but I can not find runtime anywhere to run it... Can you not use runtime if you have full blown access installed ? Or am i just having a blonde moment ???
Hi all. I have problem with form for viewing pictures. If I use apllication using full MS Access I haven't any problem. I can see BMP, JPG, GIF ... But if I open appllication using runtime I cannot open JPG file. Runtime show error to transfer picture to GIF or BMP. Where is the problem?
if I don't buy office Developer software, I just download Access Runtime 2002 from the Microsoft website, and then install it on the client machines. Do I commit the company rules? Do I need to buy unlimited license for Access Runtime before installing?
I have full version MS Access, and Office Developer Edition to disribute the Access RunTime for my clients.
I don't want to create the package (adp file), I just want to create the package for Access RunTime, and then install it into my client machines, we want to run the same adp file on the network sharing drive. Then, it's fine. But, how do I install the supported files into my client machines? Because the supported files attached to the package (adp file), if we install adp file into the client machine, it will install adp file and the supported files, but we don't want to install adp file, we just want to install supported files.
I have program compiled in Access 97 runtime installed on my Windows XP computer.
When I installed this program on account TOM (Administrator) then program run and work great. When i changed privileges for TOM (not be admin anymore) to restriction account then i have problem witch this program
URL
Program still working, but if I want to use some function in this program i have this error:
URL
I don't know why ?
In installation folder, and c:program filesMicrosoft Office Runtime 97 and c:windowssystem32 user TOM have ALL rights.
Can anybody help me ?
Sorry for my English,, i still learn it. Best regards for all
I am developing an application in access xp (2002) and want to distribute it as a runtime application. I do not have the Office xp Developer version and thus need to buy the MS Office Developer. It is still available and if so, where can I buy it? Or can the Visual Studio Tools for the MS Office System make a runtime version from access 2002? Any help would be appreciated. Niels
I have a question about Access runtime. We have some users at work who don't have Access on their machines, but we would like them to be able to use databases we have created. My suggestion was to purchase Visual Studio Tools for Office, which will give us Access Developer Extensions and allow us to distribute runtime versions of our databases.
However, the pcs here at work are pretty well tied down in terms of installing anything. E.g. no registry changes are allowed, unless you are an administrator.
So my question is - what is actually involved in installing the Access Runtime. Can it be achieved simply by copying the relevant files (ACCESSRT.* ?) into the office directory, or is there more to it than that. Will I be able to get my databases up and running myself, or is it likely that I will need the help of the Technology Department to get the Runtime installed ?
I have recently finished developing a Complaints Database for my company and we carried out some testing on machines that use runtime only and guess what? Good old runtime errors! I aksed the IT department to give me a brand new blank login profile and when I used this, the database worked perfectly under the runtime environment. This tells me that the runtime on users machines that have worked here for some time, something has changed with the way in which runtime works. What I would like to try and do is for these machines, when the database loads up, to re-install or re-configure Access runtime so it is effectively a clean Runtime slate for want of a better expression. Does anyone know how I could do this or possibly even offer any assistance in another way. My understanding of runtime is that it has most of the Access capabilities but obviously without design, build, debug functions etc and is purely a 'cloak' to allow the mdb file to be viewed/executed.
We are considering rolling out a number of access reports to users within our organisation who currently do not have access installed, nor do we want them to. Run time seems the obvious route. I see the runtime module is included in Access 2003 but I cant see if you have to install Access on the users PC in a "Runtime mode only" way or if the Developer tools have to be purchased to get the package wizard so you can send the package out with run time. Basically we want users to be able to access the database from the server but we do not want them to have the ability to do any thing else in access . i know read only rights will enable that to be done in the particular database but we don't want them building their own db's and the bothering IT when they come across something difficult....
I created an Access Runtime Database Download on Windows XP. One of my clients downloaded the db to Windows Vista. The installation went fine and he was able to populate the database with no problem. However, now he needs to send me back the data and we cannot seem to access any data files. The backend.mdb file appears to be blank, even know the data appears on the front end. We have tried searching the computer to find any hidden files it might be saving the data to and there doesn't appear to be any. I have tried copying the entire folder containing both the frontend and the backend to a jump drive and looking at the data on a different computer and it appears to be blank. This doesn't seem to happen on any other OS. Since it is a runtime version of Access, I am not able to export any files or even view anything of administrative value within the DB. When I look at the backend.mdb in Explorer, the modified date is old, so it doesn't seem to be adding the data to the backend, even though it is theoretically linked to it. Does anyone know where this data might reside or of a workaround of how to extract this data???
