SOLVED

Access 365 version 2009 build 13231.20262 query design view syntax error

%3CLINGO-SUB%20id%3D%22lingo-sub-1732133%22%20slang%3D%22en-US%22%3EAccess%20365%20version%202009%20build%2013231.20262%20query%20design%20view%20syntax%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1732133%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20start%20entering%20text%20in%20the%20criteria%20box%20of%20the%20query%20design%20view%2C%20Access%20starts%20making%20auto-corrections%20then%20tells%20me%20there%20is%20a%20syntax%20error.%20Annoying%20enough%2C%20but%20the%20error%20dialog%20box%20will%20not%20reset%20and%20allow%20you%20to%20change%20the%20text.%20The%20first%20screenshot%20shows%20the%20whole%20Access%20window.%20The%20second%20one%20shows%20that%20I%20started%20to%20type%20%22like%22.%20After%20the%20first%20letter%2C%20the%20editor%20put%20quotes%20around%20the%20l%2C%20so%20that%20when%20i%20typed%20i%2C%20it%20detected%20a%20syntax%20error%20(which%20it%20is)%20and%20then%20punished%20me%20by%20refusing%20to%20allow%20any%20more%20use%20of%20the%20database.%3C%2FP%3E%3CP%3EI%20have%20tried%20it%20with%20several%20different%20files%20and%20the%20same%20thing%20happens.%20I%20have%20rebooted%20my%20machine%20and%20updated%20Office.%3C%2FP%3E%3CP%3EI%20am%20running%20Windows%20Version%2010.0.19041%20Build%2019041%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20discovered%20this%20problem%20today%2C%20so%20I'm%20assuming%20it%20is%20a%20bug%20in%20the%20version%20of%20Access%20that%20was%20released%20on%20Monday.%20Some%20assistance%20please%20as%20it%20makes%20the%20query%20design%20editor%20unusable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Access%20error%201.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F223140iBD00BF84356E1315%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Access%20error%201.png%22%20alt%3D%22Access%20error%201.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Access%20error%202.png%22%20style%3D%22width%3A%20241px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F223139iF028CE9C831325F5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Access%20error%202.png%22%20alt%3D%22Access%20error%202.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1732133%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1742187%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20365%20version%202009%20build%2013231.20262%20query%20design%20view%20syntax%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1742187%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F815493%22%20target%3D%22_blank%22%3E%40jam_eno%3C%2FA%3E%26nbsp%3B%20It's%20been%20a%20couple%20of%20days.%20Have%20you%20found%20a%20solution%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20not%2C%20I%20am%20looking%20at%20that%20screen%20shot%20and%20seeing%20what%20appears%20to%20be%20a%20cursor%20placement%20problem.%20It%20looks%20like%2C%20perhaps%2C%20you%20started%20typing%20and%20the%20cursor%20hopped%20back%20to%20the%20initial%20position%20for%20your%20next%20letter%2C%20leading%20to%20the%20impasse.%3CBR%20%2F%3EWhen%20I've%20seen%20that%20problem%20it%20boiled%20down%20to%20a%20timer%20event%20running%20in%20a%20form.%20Disabling%20that%20timer%20eliminated%20the%20hopping%20cursor.%3C%2FP%3E%3CP%3EIf%20you%20have%20no%20timer%20events%20and%20if%20you%20haven't%20yet%20found%20another%20solution%2C%20post%20back.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1742287%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20365%20version%202009%20build%2013231.20262%20query%20design%20view%20syntax%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1742287%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126074%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3Eto%20answer%20your%20questions%3A%3C%2FP%3E%3CP%3E-%20I%20had%20stopped%20looking%20as%20I%20had%20more%20urgent%20things%20to%20do.%20My%20work%20round%20was%20to%20use%20Accesss%202007.%3C%2FP%3E%3CP%3E-%20your%20description%20of%20the%20cursor%20jumping%20back%20is%20exactly%20what%20happens.%20I%20type%20the%20first%20letter%20of%20like%20then%20Access%20immediately%20puts%20%22%22%20around%20it%20giving%20%22l%22%20and%20the%20cursor%20jumps%20back%20to%20the%20left%20hand%20end%20of%20the%20text%20box%20in%20time%20for%20me%20to%20type%20i%2C%20giving%20i%22l%22%2C%20which%20is%20indeed%20a%20syntax%20error.%3C%2FP%3E%3CP%3E-%20no%20timers%20are%20used%20in%20the%20forms%20in%20this%20application%2C%20but%20just%20to%20make%20sure%2C%20I%20closed%20all%20the%20forms%20so%20it%20was%20only%20me%20vs.%20the%20Access%20query%20design%20editor.%20Same%20effect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20your%20mention%20that%20it%20might%20be%20a%20cursor%20problem%20reminded%20me%20that%20I%20had%20recently%20switched%20on%20the%20text%20cursor%20indicator%20in%20the%20accessibility%20settings%20(see%20screenshot%20below%20if%20you%20are%20not%20familiar%20with%20it.%20My%20eyesight%20is%20deteriorating%20and%20the%20thing%20I%20have%20most%20trouble%20with%20is%20seeing%20where%20the%20cursor%20is).%20I%20switched%26nbsp%3B%20it%20off%20again%20and%20the%20Access%20problem%20disappeared.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20thanks%20to%20your%20post%2C%20we%20got%20there%20in%20the%20end.%20I'm%20not%20sure%20what%20I%20do%20now%2C%20because%20I%20found%20the%20TCI%20helpful.%20The%20answer%20seems%20to%20be%20that%20Access%20development%20is%20a%20job%20for%20people%20with%20good%20eyesight.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126074%22%20target%3D%22_blank%22%3E%40George%20Hepworth%3C%2FA%3E%20%2C%20enjoy%20the%20rest%20of%20your%20weekend.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22text_cursor_indicator_settings.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F223923i58E31774200436B2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22text_cursor_indicator_settings.png%22%20alt%3D%22text_cursor_indicator_settings.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

When I start entering text in the criteria box of the query design view, Access starts making auto-corrections then tells me there is a syntax error. Annoying enough, but the error dialog box will not reset and allow you to change the text. The first screenshot shows the whole Access window. The second one shows that I started to type "like". After the first letter, the editor put quotes around the l, so that when i typed i, it detected a syntax error (which it is) and then punished me by refusing to allow any more use of the database.

I have tried it with several different files and the same thing happens. I have rebooted my machine and updated Office.

I am running Windows Version 10.0.19041 Build 19041

 

I just discovered this problem today, so I'm assuming it is a bug in the version of Access that was released on Monday. Some assistance please as it makes the query design editor unusable.

 

 

 

Access error 1.pngAccess error 2.png

5 Replies
Highlighted

@jam_eno  It's been a couple of days. Have you found a solution?

 

If not, I am looking at that screen shot and seeing what appears to be a cursor placement problem. It looks like, perhaps, you started typing and the cursor hopped back to the initial position for your next letter, leading to the impasse.
When I've seen that problem it boiled down to a timer event running in a form. Disabling that timer eliminated the hopping cursor.

If you have no timer events and if you haven't yet found another solution, post back.

@George Hepworthto answer your questions:

- I had stopped looking as I had more urgent things to do. My work round was to use Accesss 2007.

- your description of the cursor jumping back is exactly what happens. I type the first letter of like then Access immediately puts "" around it giving "l" and the cursor jumps back to the left hand end of the text box in time for me to type i, giving i"l", which is indeed a syntax error.

- no timers are used in the forms in this application, but just to make sure, I closed all the forms so it was only me vs. the Access query design editor. Same effect.

 

However, your mention that it might be a cursor problem reminded me that I had recently switched on the text cursor indicator in the accessibility settings (see screenshot below if you are not familiar with it. My eyesight is deteriorating and the thing I have most trouble with is seeing where the cursor is). I switched  it off again and the Access problem disappeared.

 

So, thanks to your post, we got there in the end. I'm not sure what I do now, because I found the TCI helpful. The answer seems to be that Access development is a job for people with good eyesight.

 

Cheers @George Hepworth , enjoy the rest of your weekend.

 

text_cursor_indicator_settings.png

Highlighted

@jam_eno 
I'm glad you found the answer, even if it's not the optimal solution.

I wonder if there's not a different way to highlight the cursor, perhaps color or size, that would help tracking it without the unfortunate side effect.

Highlighted

@George Hepworth 

I have tried the cursor size setting and it helps. I was experimenting with the Text Cursor Indicator. The advantage of the TCI is that it doesn't obscure the text at the point of entry.

The irony is that the TCI didn't even work in Access. It works in the other MS Office applications: Word, Excel , Notepad and the Command window

Highlighted
Best Response confirmed by jam_eno (New Contributor)
Solution

For clarity to anyone with the same problem, the solution for me was to turn off the Text Cursor Indicator in the "Ease of Access" settings.

 

Thanks to @George Hepworth who put me on the right track