Scott - try something for us.

In your included file, change this
vLoadSortSpec = @SpecCommand(SPEC_OPERATION_LOAD, SPEC_TYPE_SORT, "Workorder # Descending")

to this
vLoadSortSpec = @SpecCommand(spec_operation_load, spec_type_sort, "Workorder # Descending")

and tell me if it works.

Note that all I did was make the use of the defines lowercase.

Version 2.5 includes a significant optimization to compiling when #define is in use. In the process, a piece of case-sensitivity snuck in. It's very specific and I'll surprised if it affects even six people.

In a nutshell, the use of defined constants in executable code contained in external files and then included will cause a compile error unless they are typed in all lowercase.

Infinity wrote on Sep 18^th, 2009 at 8:00pm:


That would be overkill. Instead, try to use include files for defines and only include executable code that you are using across multiple applications (in which case the defines used will need to be in lower case until we get the next release out).

Infinity wrote on Sep 18^th, 2009 at 8:17pm:


If you look in the sbasic_include.sbas file, you will see that most of the lies start with #define. This is a define. It defines something like SPEC_OPERATION_LOAD as a less human-readable value like 0. That way, you can use the define in your code, like this:
vLoadSortSpec = @SpecCommand(SPEC_OPERATION_LOAD, SPEC_TYPE_SORT, "Workorder # Descending")

You can clearly see what spec operation you are using, but Sesame sees it as 0.

The only thing affected by this issue is where you actually use the define in your executable code. The red text above indicates where this is. Nothing else will be affected by the case issue.