After allot of hair pulling and trying various methods I have discovered that there is some major problems with TYPE's in DBP. Hopefully someone can help make sense of this.
Problem 1: I recently created a program that has 4 FUNCTIONS within it. All the code was stored in the main .dba file for ease of coding and testing. Next I take the functions and place them in a second file to be #INCLUDED. Here's were the hair pulling starts. I start to get errors such as "#100008: Parameter for "text width" do not match 'String' inside lms-functions.dba.
Then if I monkey around with the lines of code that utilize the Text Width commands by not using my UDT's and I start to get errors in other areas such as "#100008: Parameter for 'BOX' do not match 'Left,Top,Right,Bottom' inside lms-functions.dba. And the list goes on everytime I get temporarily work around an error.
Problem 2: This problem I believe sheds some light on problem 1. It seems that when using UDT's there is some issues with Boolean and Byte variables. Strange results appear until the variables are changed from Boolean or Byte to integer than the problems go away. There also seems to be issues using the NOT statement in conjunction with a UDT that has variables of the Boolean or Byte type within itself.
I am a VB programmer by trade so I am very well versed with UDT's. I have tried shifting my TYPE declerations from the main .dba file to the INCLUDED file along with my GLOBAL declerations and a few other things but nothing seems to be helping.
Here is an example of one of my lines of code.
mnu(mnuSet.count).endX = mnu(mnuSet.count).startX + (text width(mnu(mnuSet.count).name) + mnuSet.spacing)
I have come across a few other small problems while working on this project but I can't remember them all at the moment.
Hopefully someone can shed some light upon my dilemma.
