[AccessD] Translation data length (cache used)

Rocky Smolin at Beach Access Software rockysmolin at bchacc.com
Sat Feb 21 11:40:06 CST 2009


The Chinese is double word length per character I think.  Did you account
for that?

Also, I haven't tested your app with Chinese yet.  Does it display OK?  You
have to have the East Asian language package implemented in Windows.


Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com
www.bchacc.com
 
 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Saturday, February 21, 2009 9:28 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Translation data length (cache used)

Using the following function I calculated the lengths of all of the
translation strings in every translation field:

Function mTotalDataLength()
Dim db As DAO.Database
Dim rst As DAO.Recordset
Dim lngDataLength As Long
Dim intFld As Integer
     Set db = CurrentDb
     Set rst = db.OpenRecordset("tblLanguage-Controls")
     With rst
         For intFld = 4 To 8
             .MoveFirst
             While Not .EOF
                 If Not (IsNull(rst(intFld).Value)) Then
                     lngDataLength = lngDataLength + Len(rst(intFld).Value)
                 End If
                 .MoveNext
             Wend
             Debug.Print intFld & ":" & lngDataLength
         Next intFld
     End With
End Function

mTotalDataLength
4:43879
5:56558
6:69133
7:107050
8:140369

Spanish and French are by far the most verbose.  In any event, if you are
caching the data for every single form for a single language, the total data
cached is about 140K.

--
John W. Colby
www.ColbyConsulting.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list