Subform records shake if the number of records is large

[Matin_Murad]

Enter the highest numbers into the lower rectangle, then enter. When you reach 9 numbers, the subform will vibrate....

 

[The_Doc_Man]

Doesn't do anything for me. No shaking or other strange behavior.

 

[Gasman]

I can't be doing it right?

 

[MajP]

Interesting that @docman can test this.
The issue most definitely deals with non-latin characters IMO.
Most people on english or latin based languages will get the error shown by @Gasman. I do too.
Here is the discussion why and a way to potentially fix it which is not quick.

Problem "With Communicating with OLE Server" Using Non-Latin Alphabet Databases

I kind of stop helping people on this site that post databases not developed in a Latin alphabet based database (examples Arabic, Cyrillic), because I run into too many problems that cannot be fixed without a rebuild from scratch. The problem I see often is this message when I try to modify...

www.access-programmers.co.uk

 

[MajP]

I do not know if there is some setting latin based dbs can apply to avoid this error. I thought there was some settings for Unicode standard and ANSI but I do not see anything. The only thing I see is maybe some language settings.
@The_Doc_Man do you have any languages loaded.

But if someone want to fix it then follow @sonic8 advice. At least it worked for me.

Save the form as a text file and it will be obvious.

So where you see something like Caption with a non-latin property, put a latin alphabet text.
Then Loadfromtext once you fixed all non-latin Names or property values.

Actually I do not think it is the properties that you need to worry about, but definitely it is the Names of objects
The below is definitely a problem

So do a text find on "Name =" and validate all of the object names

For those developing in non-latin languages
ALWAYS USE LATIN ALPHABET FOR ANY OBJECT NAMES if you want others to look at it.

 

[The_Doc_Man]

@The_Doc_Man do you have any languages loaded.

Not that I recall, but the kit I'm using is Office 2021 LTSC originally from Germany and bought through a Canadian reseller. I'm pretty sure I did NOT choose an alternate language, because Office doesn't support Cajun French. All I think I have is English.

Just for clarity, it gives me the usual warnings about code being disabled. I tried it both ways, launching Access separately for "with" and "without" code enabled. No difference.

EDIT: Went back and checked: File >> Options >> Language... same as MajP's display. English for both option boxes.

 

[isladogs]

I do have several other languages installed including Greek.
As an experiment, I replaced all Arabic object names and captions and changed the Office language to Greek
I still get the error message

Perhaps @The_Doc_Man was entering data directly into the subform which works without error

 

[The_Doc_Man]

After reading what others said, I was able to reproduce the displayed error, but nothing "vibrated" when I hit the enter key. Colin, you are correct. I guess I didn't understand the instructions.

When I looked at the properties of the subform, I noted that it pointed to something for which there is neither a table entry nor a query entry nor a macro entry. The Latin-alphabet name was fary2, and I only saw a fary1.

 

[MajP]

As an experiment, I replaced all Arabic object names and captions and changed the Office language to Greek

I tried the same workarounds, and cannot "fix" this database. However, In the past I have been pretty successful in just changing the Object names to ensure they use Latin characters and getting it to work. This one I cannot get to work. I get this error pretty consistently when OPs have non Latin dbs.

 

[Matin_Murad]

It was explained in the video that when entering data there is vibration in the records... Is there a solution to stop the vibration of the records when entering data... And thanks to everyone

 

[MajP]

I am not sure we can help much since most of us cannot run the code and replicate the issue because of the language incompatibility.
Because the actual code is very simple, my guess it has nothing to do with the code. I am guessing it has to do with the extensive use of calculated fields. Most people do not use them and they can be problematic. I am guessing when you move to a new record it is triggering a recalc of all of those fields.
1. I would get rid of all the calculated fields.
2. Get rid of all lookup tables
3. Get rid of all names and properties that use non latin characters. They can be used in captions or visible properties.

 

[isladogs]

The video shows the form flickering as it updates. This is a common issue
Try using Application. Echo False before updating then set True afterwards. Ot use Me.Painting = False followed by Me.Painting = True

 

[June7]

MajP, when you say "get rid of all lookup tables" did you really mean "get rid of all lookup fields"? Because surely the tables should remain?

 

[MajP]

MajP, when you say "get rid of all lookup tables" did you really mean "get rid of all lookup fields"? Because surely the tables should remain?

yes should have said fields.

 

[mike60smart]

I can't be doing it right?
View attachment 120288

I get the same error as Gasman

 

[Pat Hartman]

Wonder why Access even allows non-Latin characters in object names and variable names if they cause problems when switching character sets.

I remember working with COBOL in Kuwait. I'm not sure IBM had an Arabic compiler at the time. All I know is they were using an English version of the compiler although our forms and reports all used Arabic characters in the labels and data entry was right to left.

 

[MajP]

Wonder why Access even allows non-Latin characters in object names and variable names if they cause problems when switching character sets.

I remember working with COBOL in Kuwait. I'm not sure IBM had an Arabic compiler at the time. All I know is they were using an English version of the compiler although our forms and reports all used Arabic characters in the labels and data entry was right to left

As I said in the other post, I unfortunately pretty much do not look at anything if I see it in Arab writing. Because I will get this error 90% of the time and it takes work to fix. This is the first one I could not fix. I had problems with Greek, Russian and Thai database too, but I could fix them by ensuring object names were Latin.

 

[isladogs]

I'll ask the Access team about this issue and see if they can suggest a guaranteed solution