Re: Very Confused by Run Time error '3075' - Help !!
Microsoft Tech Community » Access
by Cinders01
11M ago
Karl Many Many Thanks, something as simple as that !! Best Regards Adrian ..read more
Visit website
Re: Very Confused by Run Time error '3075' - Help !!
Microsoft Tech Community » Access
by Karl Donaubauer
11M ago
Hi,   The error occurs because the string passed to the filter contains a single quote in "Int'l". As the single quote is also used to delimit the complete string it is terminated after "int" and the remaining string leads to the error. There are several methods to cure this. One is to use double quotes as delimiter, e.g. like this:   Me.Filter = "[Location]= " & Chr$(34) & Me.Combo25 & Chr$(34)   However, if your strings can also contain double quotes then you'll get the same problem with these again. So, it may be more secure to double the trouble maker and thereby ..read more
Visit website
Re: Northwind Traders Developer 2.2 Template
Microsoft Tech Community » Access
by Sue_69
11M ago
@Tom_van_Stiphout thank you so much for this info ..read more
Visit website
Very Confused by Run Time error '3075' - Help !!
Microsoft Tech Community » Access
by Cinders01
11M ago
Good Afternoon   I have a 3 line piece of code in my After Update for a Combo-Box which has always worked in the past,  I am creating a new DB this morning and utilized the same code, and am now getting a run time error 3075 and the following message :-   Syntax error (Missing Operator) in query expression ' [Location]='Belem Val de Cans / Julio Cezar Ribeiro Int'l - SEBE".   The code is :-   Private Sub Combo25_AfterUpdate() Me.Filter = "[Location]= ' " & Me.Combo25 & " '" Me.FilterOn = True Me.Combo25 = Null   Would anybody have any ideas ?   Many T ..read more
Visit website
Re: #Error in Query (nulls?)
Microsoft Tech Community » Access
by Tony2021
11M ago
Hi Karl, that worked perfectly. thanks for pointing out that its TEXT so have to change it up a little. I forgot that text is different. thanks again for pointing out the name also needed to be changed to MaxOfWithdrawalDate (thank you XPS35). I did notice that early on but thought it was not my issue since I didnt realize I also needed to account for the field being TEXT. have a good weekend! thanks for the help guys ..read more
Visit website
Re: #Error in Query (nulls?)
Microsoft Tech Community » Access
by Tom_van_Stiphout
11M ago
Although that is not your current problem: Reference is a Reserved Word, and should not be used as an object name. Just like you should not name your table "Table", or "Field". Nothing good can come from trying to confuse the Access parser ..read more
Visit website
Re: No exclusive access?
Microsoft Tech Community » Access
by Tom_van_Stiphout
11M ago
Right-click Windows taskbar, and select Task Manager. Select Details tab, sort by Name, and scroll down to msaccess.exe. I bet you there is a hidden instance running. Kill it, and try again ..read more
Visit website
No exclusive access?
Microsoft Tech Community » Access
by standenman
11M ago
I have an access database.  I am the solo user.  I had it on my laptop and I saved it to a thumbdrive and loaded to my desktop.  When I try to enter this db on my desktop I get the following:   "You do not have exclusive access to the database at this time.  If you proceed to make changes you may not be able to save them later".   since it is just me I would like to know who this other user is?  Makes no sense, but then it is Access ..read more
Visit website
Re: #Error in Query (nulls?)
Microsoft Tech Community » Access
by XPS35
11M ago
You do a lookup on WithdrawalDate, but in the query that field is renamed to MaxOfWithdrawalDate. Maybe that is (one of) the problem(s ..read more
Visit website
Re: #Error in Query (nulls?)
Microsoft Tech Community » Access
by Karl Donaubauer
11M ago
Hi Tony,   > the format is short text for both of those fields.    Ok, then I misunderstood your description. I thought you were getting the error only for some records. With this information it is clear that you should get the error for every record because the syntax for text is different than for numbers. You have to make it clear to Access that the parameter value is a string, e.g. by surrounding it with quotation marks:   WDDateGetError: DLookUp("WithdrawalDate","qryWDDate","Reference = '" & [Invoice No] & "'"   Servus Karl **************** Access Forev ..read more
Visit website

Follow Microsoft Tech Community » Access on FeedSpot

Continue with Google
Continue with Apple
OR