Change Unicode Compression Field Property

I imported an Access V1.1 database with hundreds of tables and about 4000+ fields. I want to set all fields to "Allow Zero Length" and "Unicode Compression"=true.  Should be easy! Yes?

I found loads of stuff but nothing seems to work. {?} At first I tried with DAO, then gave up. Then I tried using ADO + ALTER TABLE...ALTER COLUMN.

The I found this:

Can anybody find another working way....

Function Converter()

' Set references to ADO 2.7 and ADOX

Dim Cat As New ADOX.Catalog
Dim CN As New ADODB.Connection

CN.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + CurrentDb.Name + ";User Id=;Password=;"

Set Cat.ActiveConnection = CN

Dim TB As ADOX.Table
Dim FLD As ADOX.Column

For Each TB In Cat.Tables
    If Left(TB.Name, 4) <> "msys" Then ' ignore system tables
        For Each FLD In TB.Columns
            ' only change Text & Memo fields
            If FLD.Type = adVarWChar _
                   Or FLD.Type = adLongVarWChar Then
                    FLD.Properties("Jet OLEDB:Allow Zero Length") = True
                    ' The following causes a problem:
                    FLD.Properties("Jet OLEDB:Compressed UNICODE Strings") = True
            End If
    End If

MsgBox "Done"

End Function

LVL 17
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Try this (DAO):


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
inthedarkAuthor Commented:
I thought that DAO was dead.  But if its the only way to get things working then it lives on.
DAO isn't dead - when communicating with Jet databases, it is the more powerful (and richer) technology when compared to ADO. However, if you are using a non-Jet backend, ADO is a better solution.
inthedarkAuthor Commented:
DAO is also 2560% faster than ADO.

The first time I tried this I was using DAO from within VB6. So it works in Access but not in VB.

inthedarkAuthor Commented:
Try this:

Function MyTest()
    Dim FLD As DAO.Field
    Set FLD = CurrentDb.TableDefs("table1").CreateField("NewField", dbText, 10)
    With FLD
        .AllowZeroLength = True
        .Properties.Append .CreateProperty("UnicodeCompression", dbBoolean, -1, False)
    End With
    CurrentDb.TableDefs("table1").Fields.Append FLD
    CurrentDb.TableDefs("table1").Fields("NewField").Properties("UnicodeCompression") = True
End Function
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.