Code:
Dim varX2 as Variant
Dim varX3 as Variant
~Bunch of other code, variables, and stuff here,~
stSQL = "INSERT INTO dbo_Property" & _
"( County, kPIN, TownshipNO, TownshipNM, CycleID, CycleName, CountyClass, PropertyDesc, LevelofAssess, Type, OpenFile, KattyAssigned, Paddress1, Paddress2, Pcity, PState, Pzip5, TaxCode)" _
& "VALUES ('" & stCnty & "','" _
& stKPIN & "','" _
& stTwnNo & "','" _
& stSelTwn & "','" _
& stCycleID & "','" _
& stCycleNM & "','" _
& stSelClas & "','" _
& stDesc & "','" _
& noLOA & "," _
& stTypeNM & "','" _
& stOpenFile & "','" _
& stKattAs & "','" _
& stPaddress1 & "','" _
& stPaddress2 & "','" _
& stPCity & "','" _
& stPState & "','" _
& PZip5 & "','" _
& stTaxCode & "');"
DoCmd.RunSQL stSQL
varX2 = Nz(DLast("PropertyID", "dbo_Property"), 0) 'Grabs Primary key from Property record just created.
'CREATES ONE COOK COUNTY PROPERTY-YEAR-DETAIL RECORD USING PRIMARY KEY IN varX2 ABOVE.
stSQL2 = "INSERT INTO DBO_PropertyYearDetail" & _
"( PropertyID, TaxYear, County, TownshipNM, TownshipNO, kPIN, CycleID, CycleName, LevelofAssess, kAttyAssigned, FirstYRTriFeeP3, FirstYRTriFeeP4, SecondYrTriFeeP3, SecondYrTriFeeP4, ThirdYrTriFee, VOPTABFeeP5, CEYEAR, TaxCode) " _
& "VALUES ('" & varX2 & "','" _
& stTaxYear & "','" _
& stCnty & "','" _
& stSelTwn & "','" _
& stTwnNo & "','" _
& stKPIN & "','" _
& stCycleID & "','" _
& stCycleNM & "','" _
& noLOA & "," _
& stKattAs & "'," _
& varFYTFP3 & "," _
& varFYTFP4 & "," _
& varSYTFP3 & "," _
& varSYTFP4 & "," _
& varTYTF & "," _
& varVPFP5 & "," _
& varCEYEAR & "," _
& stTaxCode & ");"
DoCmd.RunSQL stSQL2
varX3 = Nz(DLast("PropertyID", "dbo_PropertyYearDetail"), 0) 'Grabs Primary key from Property Year Detail record just created.
~And so on~
Does this problem also exist inside of Access Queries? I have situations where I take the number of records in a table let's say 500 and multiply it times 5 and append 2,500 records into another table. Time after time it creeps up to the 32K limitation thus causing the error and alerting me to the whole issue. How is this situation handled in an Access Query?