Vista And Access 2007/2003
Jun 26, 2007
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!
Has anyone had a similar problem?
Thanks for your help!
View Replies
ADVERTISEMENT
Jun 7, 2007
I am using Access 2003 on a vista Business machine and i get an error:
'Function is not available in expressions in query expression Format([Period],"mmm-yy")'.
I also have other problems with functions in queries ie DateAdd etc.
Any solutions?
View 2 Replies
View Related
Oct 7, 2007
hi there,
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.
regards
Colin
View 2 Replies
View Related
Apr 3, 2008
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?
View 1 Replies
View Related
Nov 7, 2007
Hello,
I found a somewhat related thread but thought I would post a new one just in case my problem happens to others who were 'forced' to "upgrade" to Windows Vista Home Basic when buying a new machine....
Okay, no more complaining, here's the issue:
I have a small (8 MB) Access 2007 database stored on a machine in the office which is running Windows Vista Home Premium. There are two other machines running Windows XP Home (SP2) that can connect to the Access 2007 database with no issues.
But on my Dell Inspiron Vista Home Basic machine, I cannot successfully open the database stored on the Home Premium machine. I CAN see this database, I can see other files and open/copy them, but I cannot open the database. I am attempting to do this using the wireless connection.
I tried running these two commands as the administrator (found on another forum) because I think this is more of a network problem rather than an Access 2007 problem specific to Windows Vista Home Basic
netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
But these two commands did nothing.
I should also point out that when this database is stored on an XP machine (one of the others in the office) the database opens just fine on this Vista Basic machine!
I'm confused and frustrated! Any help is very much appreciated.
Thank you,
Mike
View 8 Replies
View Related
Dec 29, 2007
all my access 2003 project stoped working. i have massage that missing file DTE.OLB.
View 2 Replies
View Related
Jan 29, 2007
Hello,
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 can I do to solve this?
Thanks.
View 1 Replies
View Related
Jun 19, 2007
Attached is a screenshot of the relationships in a database I built a couple of years ago. It's worked absolutely fine in Access 2003 and currently has over 18,000 customers with associated information in it.
However, when I open the database in Access 2007 the performance is awful. All the forms are very slow to respond when tabbing between form elements. I've experimented by reducing the number of form elements calling on related data on a given page and whilst this improves performance it reduces usability - something I don't want to compromise on especially since Access 2007 should be able to cope with this.
My next question is therefore whether I've got the most efficient underlying table design and I can't see any other way of doing it than my current method so I'd be grateful for any feedback or advice anyone has.
View 2 Replies
View Related
Mar 8, 2007
Hi All,
Background Info: I developed our main department's Access 2003 split database which is on a server for 15+ Users. I've now been given Access 2007 for development -- Users still have 2003. There are also 2 other smaller databases that are not split (.mdb).
Problem: In the split database, I've saved the Application .mdb as 2003, relinked and made a new .mde. But the Users still cannot open the database. (I did this in a copy until I figure out the nuances with 2007.) The 2 other unsplit databases can be saved as 2003 version and Users can open OK.
I'm grateful for any suggestions on working with Access 2007. I've been trying to tackle the ribbon which is a whole other question.
View 4 Replies
View Related
Mar 30, 2007
Hi
I have an Access 2000/2003 database which opens up and displays correctly in Access 2007, but when I go to use the File>Print command, or for that matter any of the other pull down menu's nothing happens?
Has anyone else experienced thisproblem, or does anyone know what I am doing wrong?
Any help greatly appreciated.
Thanks
Steve
View 1 Replies
View Related
Nov 28, 2007
Our Access database is multiple user. The front end is on the local drive and the data file is on our main server. Our database has numerous queries, forms and reports accessed by command buttons or directly. Various queries are set to merge with Word documents.
What are major or annoying problems that have been encountered by converting. Our database is contains our membership information and is crucial to our operation. Detailing problems/solutions if possible would be extremely helpful. Asking for allot but very concerned about conversion.
Thanks for any input.
View 1 Replies
View Related
Apr 26, 2015
i have a database in access 2003 when i open it with access 2003 it shows data in table but when i open same table in access 2007 it shows only header rows , no data
how can i see this data into access 2007 or excel 2007.i want to link these table data with excel 2007 or access 2007 but with above problem i can't do it
View 1 Replies
View Related
Apr 1, 2007
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.
Tell me you've used it and it's wonderful.
Best to you all.
-Curt
View 2 Replies
View Related
Aug 30, 2007
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?
cheers all!
View 6 Replies
View Related
Nov 9, 2007
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???
Thanks,
Shelley
View 5 Replies
View Related
Jan 29, 2007
Will Access 2000 run on Vista? I've heard that it will, but I would like to verify that before I purchase the upgrade. I currently use Access '97.
Also, does Access 2000 have to be "product activated" like the newer versions?
Thanks.
View 1 Replies
View Related
Aug 9, 2007
I am building a DB in 2007 yet our department has not yet fully upgraded and won't be until the end of the year. Currently we are running Access 2003, will this prohibit the users that have yet to upgrade from utilizing the DB?
Sorry if this has been touched on before, but I have searched high and low and could find nothing.
- DF
View 1 Replies
View Related
Sep 19, 2007
I've created a database in 2007 but now found out that it will only be used in 2003. The database started as a template but has been modified quite a bit and also includes several macros and some vba. The problem is, when I save the database in 2003 format(from2007) it keeps all functionality when opened with 2007, however, when I open it in 2003 none of my buttons, macros, or vba work. The main project form is also very functionally different. Does anyone know of a way to get my functionality into a database that will open in 2003? I really don't want to spend the time redoing all this in 2003. I've uploaded my database if anyone wants to take a look (its split front end and back end) The front end is the one with problems.
-Ty
View 10 Replies
View Related
Feb 16, 2007
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...?
Any help greatly appreciated!
Baz
View 1 Replies
View Related
Jun 26, 2007
Wondering if anyone had tried this yet, and if so, encountered any problems. I have a few existing DB's in the office. Split with backend on server in mdb format. I am now using both 2003 and 2007... BUT.. Now that the runtime is out I would like to make my future updates in 2007. So the question is... Has anyone used a 2007 file format frontend with a 2000 to 2003 file format backend? I understand that the new field properties wouldn't be available in the mdb backend, but besides that, would they still link properly?Thanks
View 1 Replies
View Related
Dec 11, 2007
This is very strange. I have converted two computers from 2003 to 2007. I have also installed 5 2007's on to new computers. All of these are Professional XP sp2 setups. I copied over a database to woek on those computers. Originally the performance was very good, on all of the computers (but not the lowest specified converted laptop ) exitting from a form containing a subform takes 37 seconds. The word Calculating... is on the status bar. The laptop takes 3 seconds par with what it used to do.
I have transferred the 'Data' database, the 'Apps' database, Utility.mda and another .MDA. I have also transferred all the Reference executables to one of the other computers. This has not made a jot of improvement.
Has anyone any pointers. I have exhausted all the resources trying to find a solution to this one.
View 2 Replies
View Related
Dec 17, 2007
We are opening up a database that was made in 2003 with 2007. The design view gives us an error of "'' is not a a valid name. Make sure that it does not include invalid characters or punctuation and that it is not too long" Does anyone have a solution for this problem?
View 14 Replies
View Related
Apr 11, 2008
Hi
I purchased the Janus GridEx2000 component a couple of months ago and have used it extensively in an Access 2007 project. The component has an OCX for development and and OCX for distribution. I have come to the stage I wish to deploy the first version of the database and so have gone to the users machine and registered the distributable OCX control however when I run the database I get
"There is no object in this control".
I have searched google for numerous different attempts at solutions such as AutoCorrect being turned off, ensuring the ActiveXs weren't copied by deleting each control on each form and inserting a new one correctly, creating a new database and importing all the forms, tables etc into it. None of these solutions have solved the problem.
As a quick test I loaded Access 2003 and created a sample database. Put a form in it and on that form the ActiveX control. I then copied the mdb to the users machine and it worked. So I then went back to the development machine and opened the mdb in Access 2007 and created a new form and inserted the control. I then copied the mdb on to the user's machine again. The original form created using 2003 worked but the new form created in 2007 displayed the same error as above. I created a new blank 2007 accdb and again created a form and inserted the component, copied the file to the user's machine and again it didn't work displaying the above error.
When I open up the references on the users machine everything seems to be ok and it is linked to the correct ocx file which has been registered.
I am absolutely stumped and the thought of having to try and get the whole project re-written back into Access 2003 is just sickening.
Any help would be greatly appreciated.
Nick
View 4 Replies
View Related
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.
Any help greatly appreciated.
Thank you and best wishes for 2007.
Joe.
View 14 Replies
View Related
Mar 21, 2008
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.
I have turned off DEP.
How can I get MS Access 2007 to import Excel?
Thanks
Ken
View 6 Replies
View Related
Nov 26, 2007
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?
View 10 Replies
View Related
