Number Data Type with a Decimal field size bug now fixed?

%3CLINGO-SUB%20id%3D%22lingo-sub-1476517%22%20slang%3D%22en-US%22%3ENumber%20Data%20Type%20with%20a%20Decimal%20field%20size%20bug%20now%20fixed%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1476517%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20updated%20to%20Office%20Version%202006%20(Build%2013001.20%3CSTRONG%3E198%3C%2FSTRONG%3E)%26nbsp%3BCurrent%20Channel%20(Preview).%3C%2FP%3E%3CP%3EThis%20was%20released%20yesterday%20-%20June%2018th.%3C%2FP%3E%3CP%3EI%20ran%20a%20few%20quick%20tests%20and%20it%20seems%20to%20have%20solved%20the%20issue%20related%20to%20%3CSPAN%3Eusing%20SQL%2FVBA%20to%20write%3C%2FSPAN%3E%20to%20a%20%3CSTRONG%3ENumber%3C%2FSTRONG%3E%20Data%20Type%2C%20with%20a%20%3CSTRONG%3EDecimal%3C%2FSTRONG%3E%20field%20size.%3C%2FP%3E%3CP%3EThere%20is%20no%20mention%20of%20this%20fix%20in%20the%20release%20notes%20(or%20anywhere%20else)%3A%3C%2FP%3E%3CP%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fofficeupdates%2Fcurrent-channel-preview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fofficeupdates%2Fcurrent-channel-preview%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3EI'm%20going%20to%20do%20some%20more%20testing%20before%20I%20use%20this%20version%20in%20production.%3C%2FP%3E%3CP%3EHas%20anyone%20else%20seen%20the%20issue%20fixed%20in%26nbsp%3B%3CSPAN%3EBuild%2013001.20%3C%2FSPAN%3E%3CSTRONG%3E198%3C%2FSTRONG%3E%2C%20or%20am%20I%20missing%20something%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1476517%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1477135%22%20slang%3D%22en-US%22%3ERe%3A%20Number%20Data%20Type%20with%20a%20Decimal%20field%20size%20bug%20now%20fixed%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1477135%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F566935%22%20target%3D%22_blank%22%3E%40sjhudson%3C%2FA%3E%26nbsp%3BI%20was%20able%20to%20confirm%20that%20this%20is%2C%20indeed%2C%20a%20fix%20for%20this%20problem.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EKeep%20in%20mind%20that%20you%20are%20on%20the%20Preview%20Channel%2C%20which%20means%20that%20you're%20getting%20updates%20sooner%20than%20general%20release%20Channels.%20Other%20Channels%20are%20on%20track%20to%20get%20it%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

I just updated to Office Version 2006 (Build 13001.20198) Current Channel (Preview).

This was released yesterday - June 18th.

I ran a few quick tests and it seems to have solved the issue related to using SQL/VBA to write to a Number Data Type, with a Decimal field size.

There is no mention of this fix in the release notes (or anywhere else):

https://docs.microsoft.com/en-gb/officeupdates/current-channel-preview

I'm going to do some more testing before I use this version in production.

Has anyone else seen the issue fixed in Build 13001.20198, or am I missing something?

1 Reply
Highlighted

@sjhudson I was able to confirm that this is, indeed, a fix for this problem. 

Keep in mind that you are on the Preview Channel, which means that you're getting updates sooner than general release Channels. Other Channels are on track to get it soon.