Another Showstopper Bug: Field Names Truncated by Code Generator

Scriptcase 8 Bugs
#1

Further to highlighting an old bug that has not been fixed, http://www.scriptcase.net/forum/showthread.php?6840-An-old-bug-still-there , I see that the bug has now gotten worse! WHereas previously (in SC7) I was able to alias the field name to get out of trouble, this seems no longer possible.

This is the key part of the SQL, known to be working in MySQL Workbench and PHPmyadmin, in the grid:


SELECT
  [B]Allocations.ID AS AllocID[/B],
AllocSectionIndex.ID AS SectionID,
   AllocAreas.name AS AreaName,
   AllocPortions.name AS PortionName,
   AllocRows.Name AS RowName,

This is what happens when I attempt to run the grid application

Error while accessing the database:

SelectLimit(SELECT ocAreas.name as areaname,
AllocPortions.name as portionname,
AllocRows.Name as rowname,
Allocations.Number as allocations_number, …

This has effectively brought my project development under SC8 to a standstill.

#2

It’s weird. Try to alias the tables in the FROM, to do something like select a.id as areaid, a.name as areaname from tableareas a … and so on…

#3

Hi,
I’ve tried all that and more. It’s just annoying that under SC7 I can alias the field name and the code generates without errors.

I have established it only does this in grids, not forms. Also VIEWS can overcome the problem, including in SC8. However, I need this application to work with MS_ACCESS. My understanding is that MS_ACCESS views (QUERIES) are either not supported or don’t work.

But thanks for the response.

Cheers

#4

Started thinking about that and tried a single letter alias for the table name. That worked!? Two or more letters and it fails.

I also suspected that the naming of tables was at fault, i.e. table names starting with certain letter sequences, but I have eliminated that.

Anyway, I have a solution for now, so thanks for planting the seed.

Nevertheless, SC team, I raised this three or four years ago so it ought to get some attention, yes?

#5

This sounds like another unresolved bug… :frowning:

#6

I will check that! BRB!

#7

Hello,

we test and simulate your problem in our system, but we can not simulate the way you described the topic. Could you tell us more details of how to simulate your problem?