Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL forum
Answered

Programming Bulletproof Error 10052

Posted on by 900

I am trying to create a  new custom screen in Visual Studio. I used an exsisting custom screen as my starting point.

Straight in SQL, I created a new table, view and SProc.  The SProc is called x_xtl_PropContractExp_All. Below is a Grid that uses the SProc 

 On the launch of the screen I get  this error-

--------------------------
Programming Bulletproof Error 10052
---------------------------
Setaddr() has not been called for field bx_xtl_propcontract_exp.  Error in property Dbnav of control Form1.sPropContract.

 Even though I have this

Call SetAddr(LEVEL1, "bx_xtl_PropContractExp", bx_xtl_PropContractExp, nx_xtl_PropContractExp)

And

 Call SqlCursorEx(csr_x_xtl_PropContractExp, LEVEL1, "CSR_x_xtl_PropContractExp", "x_xtl_PropContractExp", "x_xtl_PropContractExp")

 What am I missing?

Thanks for all the help

  • Q Profile Picture
    Q 900 on at
    Re: Programming Bulletproof Error 10052

    Paul, your asnwer did the trick, it was a length issue. I shortened all my variables to around 10 and the error went away. THANK YOU VERY MUCH!!!

  • Q Profile Picture
    Q 900 on at
    Re: Programming Bulletproof Error 10052

    I renamed things so the error message is actually

    ---------------------------

    Programming Bulletproof Error 10052

    ---------------------------

    Setaddr() has not been called for field bx_xtl_propcontractexp.  Error in property Dbnav of control Form1.sPropContract.

    ---------------------------

    OK  

    ---------------------------

    Yes, sPropContract is a grid

  • Verified answer
    Paul Phillips Profile Picture
    Paul Phillips 590 on at
    Re: Programming Bulletproof Error 10052

    In addition to Barry's suggestions, you might also try decreasing the length of your variable names. The SL kernel is pretty picky on lengths.

    You are not allowed to have more than 17 characters for the name of a table (buffer), nor 20 characters for a column name. Also, I have found during my experience that cursor variable names can't exceed 20 characters (undocumented). There is more information in the SDK user guide (sl_sdk.pdf)  in the section titled "Microsoft SL SDK Size Limitations".

    You mention that you are creating a new screen so this shouldn't apply, but I have also seen error 10052 in a VBA customization where the comma was missing at the end of the PV property.

  • Barry Flynn Profile Picture
    Barry Flynn 3,090 on at
    Re: Programming Bulletproof Error 10052

    Q

    Note that there are two (or more?) different buffer names involved.

    The error message is for bx_xtl_propcontract_exp.

    Note that that name has a _ as the 4th to last character.

    But the SetAddr & SQLCyesorEx are for bx_xtl_PropContractExp.

    It does not have that _ as the 4th to last character.

    Note also that the error message refers to control sPropContract.

    Is that the grid?

    The implication is that  there is some inconsistency in the name you have used for that buffer.

    Barry

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

Quick Links

Anton Venter – Community Spotlight

Kudos to our October Community Star of the month!

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,558 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,647 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans