Microsoft Dynamics SL (Archived)

System Message 10050

(0) Share

Report

Posted on by Cynthia Audain

1,348

Hi,

Has anyone experienced an issue on importing customizations from a lower version of Dynamics to Dynamics SL 2015?

To be specific, I am not doing an upgrade but bring over customizations from version 7.0 to 2015 for testing purposes. All customizations are working fine with the exception of one where a custom table called xsoaddressext for the shipping address screen. It is presently working fine in version 7.0 but when I attempt to access the screen in version 2015 I am getting a "system message 10050 - the application specified size of record xsoaddressext does not match the database declared size".

A dh file was recreated and I copied over the code from 7.0 to 2015 but I am still getting the same error.

Could someone point me in the right direction to resolve this issue? Any assistance will be greatly appreciated.

Thanks

*This post is locked for comments

I have the same question (0)

All responses (14)

Answers (0)

Ajit Kannan 1,246 on at

Like (0)

Report

Hello,

Can you try to open in standard mode and see if you get the same error?.

The system not popup the error in standard mode delete the customization in the following table (customVBA and Custom2) then recreate the custom table and import the Customization's in SL 2015 environment again.

Thanks,

Ajit Kannan S R

Was this reply helpful? Yes No
Cynthia Audain 1,348 on at

Like (0)

Report

Hi Ajit

Thanks for the response.

I am not getting the error message when I am in standard mode so definitely the customization is the problem. I deleted the customization from the customvba table; I then paste in the customization code from a text file; recreated the tables but I am still getting the same error message.

Any other suggestions?

Was this reply helpful? Yes No
Butch Adams 4,763 on at

Like (0)

Report

Run this SQL command and look at MaximumRecordSize

dbcc showcontig ('xsoaddressext') with tableresults

Then, look at your dh file and see if the sizes agree. My guess is no, and that is what the error is telling you.

Was this reply helpful? Yes No
Cynthia Audain 1,348 on at

Like (0)

Report

Hi Butch

I executed the script indicated and the only columns that gave a value is the object id column with 255665050 and the scandensity column that return 100. I am not sure what those values really mean.

On looking at the dh file it shows me the string length for each field and the length varies from 10 to 30.

Should I therefore change the values in the object id and scandensity columns?

Regards

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

As an alternative to Butch's suggestion, try the following command:

sp_help xsoaddressext

This will show each table field, its type and size and compare that to your DH definitions.

Was this reply helpful? Yes No
Cynthia Audain 1,348 on at

Like (0)

Report

Hi Rick

That was done and when I look at the results and the dh file, it has the same length for each field.

However, I am still getting the error message.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Lisa, not sure what the issue is if the DH file matches what the sp_help shows. Are in of the fields in this custom table unusual types such that VB.Net and SQL are conflicting? Does the custom table have a tstamp field?

Was this reply helpful? Yes No
Cynthia Audain 1,348 on at

Like (0)

Report

Yes the custom table has a tstamp field.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Lisa, sorry, I am kind of out of ideas on this without being able to see the code for the DH file and see what the sp_help command returned. This is not that all of a complicated process and it sounds like your table is very basic with only a few fields. I have lots of custom tables created under 6.5 and migrated to 7.0, 2011 and 2015 with all kinds of field types and have not had any issue with SL 2015 and those tables. Most of my tables are accessed by programs developed using the SDK but I also have a couple of tables that are accessed in existing SL program through Customization Manager.

If you want to post the results of the sp_help command and the DH file code, I will take a look at that but it sounds like you have already done that.

Was this reply helpful? Yes No
Cynthia Audain 1,348 on at

Like (0)

Report

Hi Rick, the issue with the size of the dh file was resolved. However, on saving any information to the custom table, I am getting this error message:

System Message 10091

Cursor specified SqlReadOnly flag.

Function: sinsert(DefaultCreated)

Level: NOLEVEL

Tables(s): xSoaddressExt where CustID =

This is the code that is being used. Could you point me in the right direction to resolve this issue.

Private Sub Form1_Display()

Dim GridHandle As Integer

GridHandle = GetGridHandle("Spread1")

serr1 = VBA_Mextend(GridHandle, bxSoAddressExt, LenB(bxSoAddressExt))

End Sub

Private Sub Form1_Load()

Call VBA_SetAddr("bxSOAddressExt", bxSoAddressExt, nxSoAddressExt, LenB(bxSoAddressExt))

Call SqlCursorEx(csr_xSoAddressExt, NOLEVEL, "csr_xSoAddressExt", "xSOAddressExt", "xSOAddressExt")

End Sub

Private Sub Update1_OnUpdate(ByVal Level As Integer, ByVal InsertFlg As Integer, retval As Integer)

Dim SQLSTR$

If Level = 1 Then

If serr1 = 0 Then

row = MGetRowNum(GridHandle%)

End If

serr1 = MFirst(GridHandle%, MaintFlag%)

While serr1 = 0

bxAddress.CustID = GetObjectValue("cCustID")

bxAddress.ShipToID = GetObjectValue("cShipToId")

SQLSTR = "Select * from xSOAddressExt where Custid = " + SParm(bxAddress.CustID)

SQLSTR = SQLSTR + " and ShipToId = " + SParm(bxAddress.ShipToID)

serr2 = SqlFetch1(csr_xSoAddressExt, SQLSTR, bxSoAddressExt, LenB(bxSoAddressExt))

If serr2 = NOTFOUND Then

MaintFlag% = INSERTED

End If

Select Case MaintFlag%

Case UPDATED 'Existing line is updated

Call SUpdate1(c1, "xSOAddressExt", bxSoAddressExt, LenB(bxSoAddressExt))

Case INSERTED 'Existing line is new inserted one.

Call SInsert1(c1, "xSOAddressExt", bxSoAddressExt, LenB(bxSoAddressExt))

Case DELETED 'Existing line was deleted.

Call SDelete(c1, "xSOAddressExt")

End Select

serr1 = MNext(GridHandle%, MaintFlag%)

Wend

Call msetrownum(GridHandle%, row)

Call MDisplay(GridHandle%)

End If

End Sub

Was this reply helpful? Yes No