web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Season of Giving Solutions is Here!
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Application record siz...
Microsoft Dynamics SL (Archived)

Application record size different to db size

(0) ShareShare
ReportReport
Posted on by Jo Wykerd 1,639

Hi there,  

I have a table that was added in a previous version of SL (now on SL2011) that is giving the System Error 10050 when opening the Project Transaction Transfer screen (PAPTT).  I get the error 'The application specified size of table xpjweek (3) does not match the database declared size (7).'  I have tried to open the screen in Standard Mode, and all other Modes with 'Exclude Event Code' box ticked but still get this error when opening screen.  I have looked in tables CustomVBA, Custom and Custom2 and have found there is no customisation for this screen so i can't even export it and edit the file.  Any suggestions as to what I can do please?!

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Jo,

    I am having trouble following all the pieces here.  You said that you added a table to the application database.  I am assuming this is table xpjweek since table names starting with x are typically custom tables.  However, you are saying you get the error even when opening the screen with no customization set.  The only way to get this error is if the screen is executing a setaddr call for that table and, since this is a custom table, this is a custom table, that setaddr call must be coming from added code for setaddr.

    Setting customization mode to Standard should be bypassing any and all customizations to a screen (as you suggested).  Assuming whatever customization was done was done using VBA, then there should be an entry in the customvba table in the system database for this screen.

    As a point of reference, I have a customization to the PR employee screen that utilizes a custom table and if I set customization mode to Standard, the screen opens without my customization code so I know that works in SL 2011.

    You did not mention what version of SL you came from but I am guessing it was 6.5 which would mean the customizations need to be re-imported (or applied) due to the switch over to VB.NET.

    This all sounds like you may not be looking at something correctly here.  It sure sounds like this screen is trying to execute the customization that introduces the custom table which means there must be an entry in customvba for this screen but standard mode should be getting around that.

    The actual error implies that the table xpjweek is not the same size that customization defines it to be in the DH module addition.  The 4 byte difference implies there is an extra field in that table in the database.  You might want open SQL Management Studio and execute sp_help xpjweek to see how that table is defined in the application database and, perhaps, take out the 4 byte field and try opening the screen again.

  • Jo Wykerd Profile Picture
    Jo Wykerd 1,639 on at

    Hi Rick,  thanks for your reply.

    I have amended the size of table xpjweek in the DB to 3 as you suggested and am able to open the screen now.  The only problem is that there are no customisations exist (screen or VBA) so I am not able to change the table size in VBA as it is not there to change!  Also the screen does not exist when opening 'Export customisations' window indicating that it is not customised.  I unfortunately need to have the table as 7 long but not sure where the screen is referencing it from.

  • Jo Wykerd Profile Picture
    Jo Wykerd 1,639 on at

    Rick, just to had to my previous post, I also added the table xpjweek DH in VBA (which i copied from a screen where it works) as the correct size (7)  but still get the same error.  It seems like it is accessing it somewhere that i can't see via customise mode?!!

  • Community Member Profile Picture
    Community Member on at

    Jo,

    I made a new table customization against an existing SL screen and verified that the code went against that screen by looking at the customvba table.  When a removed the customization from that screen, customvba dropped the lines for that screen.  So, I am pretty sure that customizations should and are going through customvba.

    I am still bothered by the fact that setting customization mode the Standard is still giving you this error.  I verified that when I customized a standard SL screen and set the mode to Standard that my customization changes were ignored so why yours are not remains baffling.

    I am not familiar with your particular screen but I am now wondering if that screen possibly opens another screen (e.g., either under a button or a tab) that could even be a non-standard SL screen added as a project) and it is that screen that has the customization with the DH file using the smaller table size.  You might want to look closely at customvba for other screen ids in that table that might be related.  This is a long shot but your whole situation is baffling 9as you have found out).

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Season of Giving Solutions is Here!

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans