Access 2002 Runtime Install Asking For Windows NT SP6 Installing On Vista RC2 5840
Dec 28, 2006
Hi everyone.
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 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???
In our company we use a windows 2003 server. Our database is ms access 2002. The back end of the db is situated in a directory on the primary HD of the server. All our workstations use windows professional. The DB works great when inputting data from workstations using widows pro.
I use a vista (ultimate) laptop. It appears that when I enter data from my vista laptop at times it corrupts the backend of the db. None of the other workstations do this. Is vista a problem here in this situation?
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.
I have a listbox that another subform on the same main pulls results from the column(0) id from (using text box that pulls the list record selected)
When you click once it (listbox) shows the records in the second form for the corresponding. When you double click it opens the record of the selected (listbox)
This works great in Runtime 2010 for all my 32bit staff and vista
however in 64bit win 8 with any runtime including 2013 64bit the database listbox works for a while, then slows and then stops opening the record on double click and when I say slows it slows to a crawl speed like it is looking up the query in the subform instead of just opening the record with the double click.
I was thinking mouse double click settings but they seem fine and as I said before it works fine for a while.
Hi to everyone Im not sure which thread i should be in, but here goes :confused: i want to create a members database for members on my forum with HTML! Ive been told to make the database with ACCESS ive played for 2 days and im now acctually getting somewhere, i would like members to interacte with it ie....add there own details to it. How do i do this and how do i get it to my server, well i did upload a tester but no one could see it and its says they need to have MS installed or something like that :eek:
Hi. I've written a database which I may need to install on a lot of machines which don't have MS Access. Does anyone know of any software I can buy that creates the set up.exe files that allow people to just install it regardless of whether they have MS Access? Many Thanks
My customer has Access programs that work on their Windows 98 OS PC's, but when they try to use them on Windows 2000 OS PC's they will not work. The programs I believe were originally written in Access 97 and now they have Access 2000 on the PC's.
By not working I mean the following -
The Access program allows them to enter a document name and then the file opens in Word - BUT - when they use it in Windows 2000 it does not open the document at all. It says file not found in Windows 2000 and the file does exist.
** The reason they have Access opening files is that Access keeps track of them for auditing purposes.
Now here is something that I want to mention. On PC's that were upgraded from Windows 98 to Windows 2000 the programs work.
Can anyone here tell me what is missing from 98 to 2000 that would do this.
I've been perfectly happy with Access97 and WindowsXP.
But my laptop's circuitboards have deteriorated, and I need a new computer. I'm wondering what the real-world has to say about using Access 97 with Windows Vista. Does it run seemlessly? Please say yes.
I have an application which I've been improving since 1998. I tried a demo of Access 2007, and did not like the way my app interfaced with it, and I don't relish a whole lot of reworking. But I don't want to buy a laptop with an obsolete operating system.
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?
Hi, i have a problem with an access database, well 2 problems. first is i don't know much about databases. the second is at work we installed 3 computers in an office with windows vista o/s. they then had a company come in and install software for their business. They were using office 2000 access database on xp previously. The company installing their software copied the access 2000 database to the vista target machines, i believe they may have converted the database to access 2003 version when doing this. The problem is the database doesn't work and they have called us back in to sort out the problem. Well we installed service packs, fixes, patches etc and googled a lot but found no simlar problems or solutions, in short we are stumped. I think the database is compiled into an app or something with switchboard etc, which i think means i can't access it? anyway it opens up with a logon form to get into DB, i enter the username and password and click ok and it gives a message saying:
"the expression on click you entered as the event property setting produced the following error"
it goes on to say there may be problem with an "event,function or macro"
on vista with office 2003 it lists several possible causes which i havent access to right now.
i have now tried it on my own pc with xp pro and office 2007 and it basically gives the same message as above but the list of possible causes is reduced to this one:
"This error occurs when an event has failed to run because Microsoft Office Access cannot evaluate the location of the logic for the event. For example, if the OnOpen property of a form is set to =[Field], this error occurs because Access expects a macro or event name to run when the event is fired"
Can anyone explain or point me in the right direction of where to get a solution. I think this is something for a programmer to solve and possibly something that the original database programmers should be looking at rather than me. am i right?
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.
I have a customer that did not read my recommended hardware specs and bought a Vista machine with Office 2007 preloaded on it.
My application uses a Access 2003 database and it is working fine in the Vista environment. The database utilizes Access security and has a database password.
My problem is that I can't see any data that has been entered! I have ran queries and opened the tables, but it is as if there is no data in the tables. However, my application can still read the data...this is a very weird problem! This is a tech support nightmare!
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.
Hi there - hopefully someone can help me out, as we've got clients waiting on my response to this problem!!! :eek:
Anyway, my company produces an Access 2000 MDE which we ship with the Access 2000 runtime (just in case our clients don't have full Access installed)
We've had a number of calls saying that our app doesn't run on Vista, and the error provided points towards a reference problem. However, when I load the MDB on Vista using Access 2007, there are no reference issues.
Is this problem related to Access 2007 reference ("Microsoft Access 12.0 Object Library") somehow being used instead of the Access 2000 one? ("Microsoft Access 9.0 Object Library") - I am about to try uninstalling Access 2007 and running the app again to see if that helps...?
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'm thinking about upgrading my operating system from XP to Vista Home Basic, but curious if any users have have experianced any dramas running Access 2003 SP3 on the Vista platform? or shouldnt there be any mayjor problems.
