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?
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!
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
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 was about to post this question in Access FAQs under the following thread but it's not allowed. http://www.access-programmers.co.uk/forums/showthread.php?t=136543
I downloaded the Access 2003 VBA reference from the MS website. When it runs on my computer (XP professional), it will pop up a message box indicating a script error (snapshot attached), and made the reference contents incomplete. Has anybody experienced the same problem before and how did you fix it? Thanks.
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
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!
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
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.
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
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
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.
Heya,
In your opinion, what is the best Microsoft Access 03 Reference book for learning?
Mateo
I have a new computer with Vista Business and MS Access 2003. ALthough I'm not sure I have Access 2003 because it keeps blowing up with lugubrous error messages
1) Cannot find field ''
2) Out of Memory (I have 2GB and this happens with one dbs open)
I'm dying a slow death due to my vistalobotomy
What is the status of Office and Vista Updates?
Is anyone else having this problem?
Thanks for your help.
Basically I have this formula in excel and i'm trying to recreate it in access but i can't quite figure it out.
****a***********b**********c*********d*********e** ******f
3**Car***Cost Center****start****combining*****end*****miles
4**001*****aaa********021****=(A4&" "&C4)***030
5**002*****bbb********030****=(A5&" "&C5)***035
6**002*****aaa********035****=(A6&" "&C6)***040
f4: =IF(COUNTIF($D4:$D600,D4)=0,(E4-C4),(E4-C4)/COUNTIF($D4:$D600,D4))
f5: =IF(COUNTIF($D5:$D601,D5)=0,(E5-C5),(E5-C5)/COUNTIF($D5:$D601,D5))
f6: =IF(COUNTIF($D5:$D601,D5)=0,(E5-C5),(E5-C5)/COUNTIF($D5:$D601,D5))
So basically: If a car is using multiple cost centers for a trip it divides the total mileage among the cost center for said trip provided that the user enters the same start and end mileage on all the cost centers used. And if it doesn't have multiple cost centers it provides the appropriate amount.
=IF(COUNTIF($D4:$D600,D4)
=IF(COUNTIF($D4:$D600,D5)
=IF(COUNTIF($D4:$D600,D6)
and so on
Any way to reference a column in access while referencing a specific point within that column.
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.
I have two database applications and they are:
- the (A) application is for administration use.
- the (B) application is for normal users use.
the idea is that: I made the (A) application for administrators who have full control over the database objects (tables, forms, queries, and so on ...).
the (B) application I have created for normal users who will have only to use forms to insert some data and display data only.
but the two applications has a respective table called "vacation request" table. where I linked them, so the both administrators and users can share the data.
The real question is that: How can I prevent the users from seeing the database objects in their application. I used the database options which have helped me in hidding the database objectives when the users open the application, but unfortunately they managed to access to the database objects by pressing the special keys.
I would like to have an access to the (B) application when I want to make some modifications to the forms and then lock it from users where they only have to use the forms for requesting vacations and view the vacations.
I've been using the following code successfully in Access 2003 & now I need to migrate to Access 2010. The purpose of the code is to use the items that the user selects in the list box to build the criteria of a query. Access 2010 keeps giving me a syntax error when I try to run the query & I don't know why:
My code is:
On Error GoTo Err_Command151_Click
' Declare variables
Dim db As DAO.Database
Dim qdf As DAO.QueryDef
Dim varItem As Variant
Dim strCriteria As String
Dim strSQL As String
[Code] .....
The syntax error I get in Access 2010 is:
Syntax Error in query expression 'SELECT * FROM
qryContractListSummarybyDateContract3TYPEBREAK WHERE
qryContractListSummarybyDateContract3TYPEBREAK.Rep ortableName IN('Adbri
Masonry NSW');'
Can an Excel spreadsheet reference an Access Table for it's data? Sort of like a vlookup, but instead of referencing another spreadsheet, I'd like to pull data in from a database.
View 1 Replies View RelatedAttached 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.
I am working on a massave aplication that has been running in Access 2000, but recently several of the file sharing users have installed Access 2003 because of the limited availability of Access 2000. All the users are using the same file off the server.
The problem we are having is that when we reference a subform in the "[Forms]![FormName]![SubformName]![FeildName]" Access 2003 does not recognize it and returns an error. I have found that if I will modify it to "[Forms]![FormName]![SubformName].[Form]![FeildName]" it is recognized in both 2000 and 2003.
To try and change every instance of a subform reference will take forever and I am garuteed to overlook something. We reference subforms all over our program, missing any one of them would be a disaster. Before I went to the tedious task of looking through everything I just wanted to throw the situation out there and see if any of you had any great ideas on how to get it fixed efficiently. I would apreciate any ideas.
Important notice from Micro$oft's Knowledge Base:
When you open or are using a Microsoft Office Access database on a computer that is running Windows Vista, you may encounter one or more of the following issues:
• Access appears to stop responding.
• Access responds very slowly.
• Access exits unexpectedly or crashes.
For the complete article and possible work arounds goto:
http://support.microsoft.com/?kbid=935370
Hi All,
I have a simple form with 3 subforms. I have a 1 data field on the main form for each subtotal of the subforms as well as an overall total field.
I have the following code in the subtotal fields:
SETot=IIf(DCount("[ID]","qryExpenses")=0,0,DSum("[Reimbursment]","qryExpenses"))
DTETot=IIf(DCount("[ID]","qryTravelExpenses")=0,0,DSum("[Expense]","qryTravelExpenses"))
RTETot=IIf(DCount("[ID]","qryTravelExpensesR")=0,0,DSum("[Amount]","qryTravelExpensesR"))
The total field then contains the following code:
Total=nz([SETot])+nz([DTETot])+nz([RTETot])
The queries all run off data elsewhere on the form, and i have triggered a "Form Refresh" macro on each of the changeable fields of the form, (so for example when changing the start date for the period the form then refreshes and re-runs the queries and updates the forms.
All things work perfectly on our windows XP systems but the rare few Vista operating systems causes these form fields to have errors. Basically the 3 subtotal fields don't appear to refresh when they are supposed to, and the total field shows as "Error"
It is actually a fairly cosmetic thing as the more important reports are generated without error, but it is something i would like to fix anyway, simply to keep the masses happy.
Would be very appreciative of any assistance or idea's on what's happening, or perhaps what's not happening here.
BTW: All have MS Office 2007, None do not have Administrator access. All XP machines work perfectly, all vista machines have these errors.
Cheers
Nathan
I apologize up front for how long this is, but the queries involved are a bit complex.
I developed a database in Access 2003 running on XP sp2 to score events for our dog club. Everything works. I recently had to migrate to Vista. I installed Access without a problem. No changes to the database were made. Almost everything works except for a few queries. I continually get the error "Object invalid or no longer set." This is not running on a network - it is local on the hard drive. Setting XP compatibility mode and runing as administrator do not help.
The query that is actually causing the problem is the third in a chain, meaning it queries a dataset produced by another query, which in turn queries a dataset produced by a third query. This all works under XP.
I have narrowed the problem down to the ORDER BY statement in the query (I prefer to work in SQL). If I remove one of the sort criteria, everything works, except the results are displayed in the wrong order. It does not matter if I click the "run query" button on my form, or simply execute the query from the list of queries, the same error occurs. This is where I'm stuck.
Here is the chain. This query pulls data out of multiple tables and performs some point total calculations. This one is rather complex, but works fine. It produces a blob dataset of all entries for all events and sets points for each entry.
SELECT tblResults.Event_ID, tblEvents.Event_Name, tblClass.Class, tblDogs.Dog_Name, tblDogs.ID, tblDogs.Owner, tblDogs.Sex, tblResults.Dog_Wt, tblResults.Cert, tblResults.Ex, tblResults.Cplt_Wt, tblResults.Time, tblResults.Final_Wt, tblResults.Dist, tblResults.Place, IIf(tblResults!Cplt_Wt<400,0,5) AS Bonus, IIf([Bonus]=0,0,IIf(tblClass!Class="D",(tblEvents!D_Count-(tblResults!Place-1)+[Bonus]),IIf(tblClass!Class="C",(tblEvents!C_Count-(tblResults!Place-1)+[Bonus]),IIf(tblClass!Class="B",(tblEvents!B_Count-(tblResults!Place-1)+[Bonus]),IIf(tblClass!Class="A",(tblEvents!A_Count-(tblResults!Place-1)+[Bonus]),(tblEvents!O_Count-(tblResults!Place-1)+[Bonus])))))) AS Points, Round(tblResults!Cplt_Wt/tblResults!Dog_Wt,2) AS xbdywt
FROM tblClass INNER JOIN (tblEvents INNER JOIN (tblDogs INNER JOIN tblResults ON tblDogs.ID=tblResults.Dog_ID) ON tblEvents.Event_ID=tblResults.Event_ID) ON tblClass.Weight=tblResults.Dog_Wt;
That resulting dataset feeds the next query, which also works fine. This one sums the points for each entrant by class for the season, only selecting entrants that have been in 3 or more events.
SELECT DISTINCTROW qryAll_Results.Class, qryAll_Results.Dog_Name, qryAll_Results.Owner, Sum(qryAll_Results.Points) AS Points
FROM qryAll_Results INNER JOIN qryPulls_Entered ON qryAll_Results.ID=qryPulls_Entered.ID
WHERE qryPulls_Entered.CountOfID>3
GROUP BY qryAll_Results.Class, qryAll_Results.Dog_Name, qryAll_Results.Owner, qryAll_Results.ID;
This last query is the one causing the headache. This one pulls the 10 entrants with the most points for a class, sorts them by points, then assigns 1st-10th place.
SELECT TOP 10 qryOverall_Totals_All_Classes.Dog_Name, qryOverall_Totals_All_Classes.Owner, qryOverall_Totals_All_Classes.Points, ((SELECT COUNT(*) FROM qryOverall_Totals_All_Classes AS T WHERE T.Class = "A" AND T.Points > qryOverall_Totals_All_Classes.Points)+1) AS Place
FROM qryOverall_Totals_All_Classes
WHERE (((qryOverall_Totals_All_Classes.Class)="A"))
ORDER BY qryOverall_Totals_All_Classes.Class, qryOverall_Totals_All_Classes.Points DESC;
If you remove 'qryOverall_Totals_All_Classes.Points DESC' from the ORDER BY statement, the query runs. If you leave it in, it generates the error "Object invalid or no longer set". I've tried using the alias, but that didn't work either.
Any thoughts? I can post the database somewhere if someone needs to see the whole thing.
I upgraded a 2000 db to 2003 recently. When I ran the function below it gave me an error on the line in green. Any thoughts? Thanks.
Const FIRSTROW = 13
Dim wsp As Workspace, dbv As DAO.Database, tblResolve As DAO.Recordset
Dim tblVchs As DAO.Recordset, tblImpTmp As DAO.Recordset
Dim ObjXLApp As New Excel.Application
Dim FileToOpen As String, WhereCriteria As String, ImportTemp As String, tmpVch As String
Dim TotalDupes As Integer, TotalGood As Integer, TotalRejects As Integer
Dim TotalBlank As Integer, R As Integer, C As Integer
Dim BadSheet As Boolean, ImpFail As Boolean
Dim tmp, tmpType, tmpCtr, tmpRsn
If Forms![Import Block Vouchers]![Import Program] = "0" Then
MsgBox ("You must select a Program to load.")
ObjXLApp.Quit 'Exit from MS Excel
Exit Function
End If
I have an Access DB that I created in Access XP. It works perfectly when used in Access XP. When used in an Access 2003 environment some of the functions don't work anymore. I have users who use Office XP and users who use Office 2003. Does anybody know how to make this DB work in Access 2003 without having to do wholesale code changes?
I have already changed the security to "Low" to bypass the security feature built in in Jet 4.0 but it didn't help. I might have to uninstall Windows XP SP2 to make it work because I know that the application works in an Office 2003 environment with Windows XP SP1 only. But I'm trying to avoid having to uninstall XP SP2 because it's a pain. Any ideas would be greatly appreciated.
Thank you.
My workstation environment is as follows:
OS: Windows XP SP2
Office: Office 2003 SP1
Jet: 4.0
Raneil