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.
WindowsNT 4.0 Service Pack 6 error in access runtime install I have an access runtime install package that has worked numerous times installing on XP Home. It was built using Office XP developer's packaging wizard.
I tried installing it on a brand new PC running XP Home but it generates the error: Visual Basic 6.0 Setup Toolkit The office system pack cannot be installed on this system because it requires Windows NT 4.0 Service Pack 6 or later.
Have been testing installation of Office XP Developer Access 2002 runtime package created using the package wizard on a WinXP Pro SP2 machine, for installation on a Vista RC2 5840 machine.
After installing the latest necessary updates such as Office XP Developer SP1 among others which were essential to remove the Path/File error I had, A new error displayed itself as soon as the runtime install package launched.
------------------------------------------------------------------- Visual Basic 6.0 Setup Toolkit (Error Window Title Bar)
The Office System Pack cannot be installed on this system because it requires Windows NT Service Pack 6 or later. -------------------------------------------------------------------
I assume Windows NT SP6 has no relevance to Vista ???
Maybe some other update will help here. I have googled for hours to no avail.
I have a genuine Microsoft CDs and keys, one with Office 97 Small Business Edition, and the other with Access 97 (these are both the full version, NOT upgrades). As I got new machines over the years (both Windows 98 and Windows XP SP 2), I installed the software from both CDs without incident a number of times on on each of those machines. I now have a new Lenovo T60 laptop (again with Win XP SP 2, 1 GB of RAM, and over 100 GB of free disk space).
Word, Excel and Outlook from the Office 97 SBE CD installed normally and run normally, except that I had to rename two Registry keys to get past an error message during installation saying that htmlmarq.ocx could not register itself (see http://forum.theispguide.com/isp-ftopic2753.html). When I went to install Access on the new machine, it kept prompting me to either point it to the folder where the "qualifiying product" was installed, or to insert that product's CD, before it would let me proceed with the "upgrade" - all this despite the fact that this is definitely a full product CD, and NOT an upgrade version. I went round and round with this a number of times, and eventually got past this series of screens (I don't remember how I did it, I was just so relieved to have circumvented the problem).
The balance of the installation appeared to complete normally. However, when I try to launch Access, I get an out of memory error, even immediately after a re-boot and with no other applications running. Does anyone have any ideas about how to resolve this?
Recently I copied a database to another machine at a client. First problem, the open report command canceled, then thining I had a code problem I tried to open the report from the menu. It will not open or allow me to go into design mode, althouh forms and queries will NO reports will allow this. The when I try to open the forms in design mode they crap out with a msacces.exe aborted mesage.
This database works on 53 other macines so it has to be something paculiar to this particular machine. I have tried a complete unisnstall and install twice to no avail.
I'm setting up a DB for my wife's machine shop. She has Windows 2000 (for accounting purposes) and her assistant has XP. I have 2000 at home so I installed Access 2003 on my computer, created the database, table, query, macro, and switchboard, and it works great. Problem? Apparently, I cannot use the same product key more than twice. I installed it on my wife's machine, but couldn't activate it on her assistant's machine.Microsoft says this is in the end user license agreement, and I'll have to take their word for it cuz I didn't read it.
My question: Is there some sort of workaround for this? If I deactivate it/uninstall it on my machine will that help? I don't need it now that the db is set up anyway. I just need to get it activated on the 3rd (assistant's) machine ASAP.
Hello, Is it possible to install two versions of MS Access on the same O.S. I already have Access97 installed. Now I want to install access 2003 without it up removing my previous access 97. If it removes/upgardes access 97 to access 2003 I will not be able to open my access 97 database. Is this possible? and if so how?
I use Access 2003 and Access developer extensions for packaging the software(operating system is Windows 2000)..everytime I upgrade my software, the users need to uninstall it from their computer and then install my new version.. Is it possible to automate this process so that users click a button on the application and uninstall and install is taken care?
I know I can run a batch file using shell command...but can I create a bat file to uninstall and install? Now, users goto add/remove programs and remove their current version before they install new version.
Hello, Is it possible to install two versions of MS Access on the same O.S. I already have Access97 installed. Now I want to install access 2003 without it up removing my previous access 97. If it removes/upgardes access 97 to access 2003 I will not be able to open my access 97 database. Is this possible? and if so how?
In have a db that was created with Access 2003. I recently installed Access 2007 and kept the old version as well. However, when I try to work with the db in Access 2003, I am getting all kinds of errors. When I run the same db in a machine installed only with Access 2003, it runs fine. I am thinking that it might be the reference library. Can anyone help. If it is the reference library, how can I revert back to the old reference library.
Environment WInXP Pro SP1, MS Access 2003, existing access project that fires on another PC with similar setup.
Just installed MS Access 2003 to my own PC. When I try and open an existing project am being informed I need to upgrade jet 4.0 to service pack 8. When I try and install jet SP8 windows is telling me I already have a later version :confused:
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???
