I have packaged my Access 2000 program using SageKey. When I open the installed runtime version of the database, and click on a menu button that performs a databse backup, there is no error, yet the file does not copy (note that I am using a function that utilises apiCopyFile). It does not do this in the full Access version where I have developed the program. Does anyone have any idea why it is doing this? And any suggestions to how I could fix this or change my approach?
I have a Access front end connected to a MS SQL database using a ODBC connection which is working fine of course.
When I compile it as a runtime version and install it on the business computer I get an error with the ODBC connection (I can't remember exactly what pops up). On the business computer I have installed SQL Native Client and in the ODBC added a System DSN (which works).
I created a small database with a user login form, along with a password reset form. Running it in my sandbox as an accdr file, the password value resets just fine, but on my test machine with the Access 2010 runtime installed, the password reset form doesn't reset the password. I will try to describe the state of things as of this point.
1. The LoginF presents with a combo box for the user to choose their name, and a text box to enter their password. The code below is on the After Update of the password text box.
Code: Private Sub txtPassword_AfterUpdate() 'Check if user has been chosen If IsNull(Me.cboUser) Then MsgBox "Please Select User Initials", vbInformation, "Warning"
[Code] ....
2. The password reset form has two text boxes for the new password and to re-enter the same, as well as a command button with this code.
Code: Private Sub cmdResetPassword_Click() If Me.Password = Me.PasswordTest And Len(Me.Password) & "" > 0 Then DoCmd.RunCommand acCmdSaveRecord DoCmd.Close DoCmd.OpenForm "LoginF"
[Code] ....
As I say, this works as an accdr file, but not in the actual runtime environment.
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.
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???
Does anyone have a good easy sugestion on how to distribute a db with access runtime in a package to users without access 2003? I have tried setup2go and it makes a fine .exe file. But I can't make the package with access runtime.
I am reading this forum for a while now and I learned here almost everything I know. But, now i am having problem and I really don't know how to solve it. I am trying to test some little program which I made fo my company. It is Access 2000 database and I made it with Access 2003. Everything is working 100% in Access 2003. BUT, problem is that this database will be run on several mashines in two of our companies and in that other company they have a lot of computers with Win98 installed. I have Access 2003 Developer and I managed to make deployment for computers in my resident company, but, as you probably know, Access 2003 is not working on Win98 computers.
So, I tried to install Access 2000 Runtime on those computers and I am still trying because stupid installation won't finish! It just stops when it comes almost to the end of instalation and nothing happens. I tried to wait for some time but instalation is dead. I also tried to make clean instalation of Win98, but nothing changed. There is no Access on those computers of any kind.
I tried to search forum for solution, but I didn't find it.
I have been writing databases for several years now, so I know my way around access pretty good. I have come upon a strange error though. which is confusing me to now end. I wrote a Database on my work machine which has the latest version of MS Access and SP2 for Office. I just tried to send it to another employee for them to test. Now they do not have the full version of MS Access installed on their machine, they only have the runtime version which only runs the Database. The load works fine and the first screen uses ADO to lookup some value and display them in a list box, nothing crazy, everything works fine. Now using this form, when they click a button the info in the list box is used to set the Fields a new Unbound form. And this is where the error happens. The on_load event of the form fails for some reason, and gives a msgbox which says, "Runtime error occured and the App needs to close", but the prog works fine on my machine. I am baffled. The file is a MS Access 2000 format, I tried changing it to MS Access 2002/2003 Format, and when I do that they cannot open the file because it says they do not have thje latest MS Access version. I have no idea what, why the error occurs, any ideas??
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.
-------------------- 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 ----------
We have a split db with the BE on a server and the FEs on the client pcs which are all running Access Runtime
I set up users on the database with different access permissions but when I open the FE in Access Runtime it doesnt ask for login credentials and just allows full read/write access to any user.
Can Access Runtime be set up for different logins/passwords?
I have three terminal servers in a cluster. One of them already has MS Access runtime 2000 installed and working. I am attempting to install it on the other servers. I have done this using the terminal server .mst file and in conjunction with the .msi installer. All appears fine until you try to run an Access application and it states 'cannot find system.mdw' however the other server (working) doesnt have this file either. In the 'add/remove progs' list, Access runtime is listed as being installed.
In Microsoft article 291264, it says "In a run-time application, the front-end and back-end databases must be stored in the same folder."Is that really true or am I misconstruing the article?I want to use runtime clients with a split back end on a share drive.
I have access 2003 and I package my application with Access runtime. Users do not have access installed in their computers.
The problem the users have is, they cannot Copy/Cut/Paste from the textbox controls in the application..The same application when I run using my full version of Access 2003, I can cut/paste...
Is there a way to fix it without having to get full version of access ? or I have to live with it because I use access runtime.
