Creating fields in a new table.

[sjones]

I have discovered that creating a field in VBA code as dbDecimal causes an
error but creating it as dbBigInt works fine. After appending the table the
field properties (in code) show dbDecimal.

Anyone have more information about this issue.

 

[sjones]

Now I have found that the Size is dbBigInt while the type is dbDecimal.

 

[sjones]

I am trying to create a Decimal field from code. I appears that the
CollatingOrder property is where the Precision is stored. But that is read
only from code. Any way to change that?

 

[Marshall Barton]

I have discovered that creating a field in VBA code as dbDecimal causes an
error but creating it as dbBigInt works fine. After appending the table the
field properties (in code) show dbDecimal.

Anyone have more information about this issue.

Yeah, I frequently stumble over these things too. Maybe
Help is kind of schizophrenic about DAO and ADO or maybe the
Help writers just couldn't keep up with the programmers :-\

 

[Marshall Barton]

TTBOMK, the Precision and Scale properties have never
incorporated into the DAO object model.

You might want to explore the ADO (and ADOX?) library, but I
can not help you with that so start a new thread if you have
further questions.

 

[sjones]

Now I have created the Precision and Scale properties which show up just fine
in table design view just as expected and when I debug.print the table
properties they are listed just as expected.

But when I change anything thing in the table design view and save the table
the Precision and Scale disappear and CollatingOrder is changed to Precision.
I still can not find out where Scale is stored. (Could it be in the
ColumnWidth?)

TTBOMK, the Precision and Scale properties have never
incorporated into the DAO object model.

You might want to explore the ADO (and ADOX?) library, but I
can not help you with that so start a new thread if you have
further questions.
--
Marsh
MVP [MS Access]

I am trying to create a Decimal field from code. I appears that the
CollatingOrder property is where the Precision is stored. But that is read
only from code. Any way to change that?

 

[Marshall Barton]

My guess is that it is stored in an unexposed property so
you will never find it using DAO.

AFAIK, the Decimal data type is only supported in VBA and
DAO through the use of the CDec() function.

I believe that you are only going to get what you want by
using ADO to Execute a SQL DDL statement.

Allen Browne has some information on Decimal fields:
http://allenbrowne.com/ser-49.html
http://allenbrowne.com/bug-08.html
http://allenbrowne.com/func-ADOX.html#CreateTableAdox