Problems passing my App to the movile device & Problems with memory tables (DADataTables)

Data Abstract
1

Hi there,

I’m doing a RemObjects client in iphone and i wondering why the compiler of xcode have the following result when i try to pass the app to the movile device:

Apple LLVM compiler 3.0 Error … clang failed with exit code 1.

I did a test, reducing remote methods to my rodl and it’s works. My question is, exist a way to configure the compiler to support compilation to big files because my intf.h have 30000 lines of code and my intf.m have 260000 lines of code.

My other question is regarding a management of a DADataTable without structure send by server to the client. The situation is the following:

I have two memory tables (DADataTables), the first received the data from the server. The fields are in disorder and for that i need a second memory table with the position of the fields correctly. The first problem is when i try to do a merge between two tables nothing happens ( I have the same structure regarding of the definition of the fields and i have the same primary key in the two tables).

For that case i emptied the data of the first table to the second manually, then when i try to do a postAll to the second DADataTable the set of DADataTableRow remain with delta change enabled. I tried to change the DADeltaChanged changing the status to csResolve without effect.

Do you have any idea that what is wrong?

Thanks and see you later…

2

Hi,

regarding first part of the question:
It looks like a bug or limitation of the Clang analyser, so I’m afraid we cannot do much here. You should report this to Apple.

Regarding second part of the question:
I’m not sure I understand why do you need two separate tables for keeping the same data.
It will be an extra overhead, especially for mobile devices, where memory is limited.

Does the fields order important on your client side?
You can bind any fields of your first table to any of your UI controls and fields order should not affect on binding.