SOLVED

Problem in Table with datatype decimal

%3CLINGO-SUB%20id%3D%22lingo-sub-1448132%22%20slang%3D%22de-DE%22%3EIssue%20in%20Table%20with%20datatype%20decimal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1448132%22%20slang%3D%22de-DE%22%3E%3CP%3EIn%20Access%20i%20have%20the%20following%20Table%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Etbl_Test%3A%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3BID%3A%20Car%20value%3B%20%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3BField1%3A%20Short%20text%3B%20%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3BField2%3A%20Number%20(Long%20Integer)%3B%20%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3BField3%3A%20Number%20(Decimal%2018.0)%3B%20%3CBR%20%2F%3E%26nbsp%3B%20%26nbsp%3BField4%3A%20Number%20(Long%20Integer)%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBy%20executing%20the%20following%20sub%20Access%20crashes%20after%20the%20Debug.Print%20of%20Feld2%20ab%20(seems%20it%20has%20to%20do%20wihth%20the%20datatype%20decimal%20of%20this%20field)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPublic%20Sub%20Test()%20%3CBR%20%2F%3E%20Dim%20rs%20As%20DAO.%20Recordset%20%3CBR%20%2F%3E%20Dim%20F%20As%20Field%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20On%20Error%20GoTo%20Error%20Set%20rs%20%3D%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20CurrentDb.OpenRecordset(%22SELECT%20*%20FROM%20tbl_Test%3B%22%2C%20dbOpenDynaset%2C%20dbSeeChanges)%20%3CBR%20%2F%3E%20If%20Not%20rs.%20EOF%20Then%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20For%20Each%20F%20In%20rs.%20Fields%20%3CBR%20%2F%3E%20Debug.Print%20F.Name%20%26amp%3B%20%22%3A%20%22%20%26amp%3B%20F.Value%20%3CBR%20%2F%3E%20Next%20F%20End%20If%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%20Error%3A%20If%20%3CBR%20%2F%3E%20Err.Number%20%26lt%3B%26gt%3B%200%20Then%20MsgBox%20Err.Number%20%26amp%3B%20%22%20%26amp%3B%20Err.Description%20End%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20Sub%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1448132%22%20slang%3D%22de-DE%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1448434%22%20slang%3D%22de-DE%22%3ESubject%3A%20Problem%20in%20Table%20with%20datatype%20decimal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1448434%22%20slang%3D%22de-DE%22%3E%3CP%3EMeanwhile%20i%20found%20out%20that%20it%20seems%20to%20be%20a%20bug%20in%20Access%20version%202005.%20In%20the%20previous%20version%20the%20problem%20does%20not%20exist.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1448521%22%20slang%3D%22en-US%22%3ERE%3A%20Problem%20in%20Table%20with%20datatype%20decimal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1448521%22%20slang%3D%22en-US%22%3EThere%20have%20been%20a%20number%20of%20similar%20reports%20regarding%20this%20version.%20The%20current%20recommendation%20is%20to%20roll%20back%20to%20a%20prior%20build.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1470659%22%20slang%3D%22de-DE%22%3ERE%3A%20Problem%20in%20Table%20with%20datatype%20decimal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1470659%22%20slang%3D%22de-DE%22%3E%3CP%3EDoes%20anyone%20know%20when%20Micrsoft%20is%20expected%20to%20fix%20the%20bug%3F%20Our%20company%20does%20not%20roll%20back%20to%20an%20earlier%20build.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

In Access i have the following Table:

 

tbl_Test:


   ID: Autowert;
   Feld1: Kurzer Text;
   Feld2: Zahl (Long Integer);
   Feld3: Zahl (Decimal 18,0);
   Feld4: Zahl (Long Integer);

 

By executing the following sub Access crashes after the Debug.Print of Feld2 ab (seems it has to do wihth the datatype decimal of this field):

 

Public Sub Test()
Dim rs As DAO.Recordset
Dim F As Field

On Error GoTo Fehler

Set rs = CurrentDb.OpenRecordset("SELECT * FROM tbl_Test;", dbOpenDynaset, dbSeeChanges)
If Not rs.EOF Then

For Each F In rs.Fields
Debug.Print F.Name & ": " & F.Value
Next F

End If


Fehler:
If Err.Number <> 0 Then MsgBox Err.Number & " " & Err.Description

End Sub

3 Replies
Highlighted

Meanwhile i found out that it seems to be a bug in Access Version 2005. In the previous Version the problem does not exist.

Highlighted
Best Response confirmed by HartwigSch (New Contributor)
Solution
There have been a number of similar reports regarding this version. The current recommendation is to roll back to a prior build.
Highlighted

Does someone know when Micrsoft is expected to fix the bug? Our company does not roll back to an earlier build.