CreateTable fails while creating a data table.

3600
3
Jump to solution
09-21-2015 04:56 AM
BharatKale
New Contributor

Hi,

I have and xml definition for a data table. Till API1.3, everything used to work fine but, when I upgraded my API to V1.4, CreateTable is failing for the same XML (Attached schema.xml).

I compared with the table.xml that is delivered in the XML samples along with the API and made modifications so that table.xml looks exactly same as schema.xml (attached both the files and they are absolutely same). when I give table.xml everything works fine but when schema.xml xml is used CreateTable is failing with the error "General Function Failure" (hr= -2147467259)!!

Can you any one help if I'm missing anything here.

Thank you for your time.

Regards,

Bharat

0 Kudos
1 Solution

Accepted Solutions
LanceShipman
Regular Contributor

<CLSID>{52353152-891A-11D0-BEC6-00805F7C4268}</CLSID>

should be:

<CLSID>{7A566981-C114-11D2-8A28-006097AFF44E}</CLSID>

You may want to look at the creation of the streets feature class in theTableSchema exanple in the samples. Creating a table is even simpler as you just create the fieldDefs and pass it to create. All the complication is in creating the coordinate reference and geometry, which with a table is not required,

View solution in original post

3 Replies
LanceShipman
Regular Contributor

I'll take a look.

Lance

0 Kudos
LanceShipman
Regular Contributor

<CLSID>{52353152-891A-11D0-BEC6-00805F7C4268}</CLSID>

should be:

<CLSID>{7A566981-C114-11D2-8A28-006097AFF44E}</CLSID>

You may want to look at the creation of the streets feature class in theTableSchema exanple in the samples. Creating a table is even simpler as you just create the fieldDefs and pass it to create. All the complication is in creating the coordinate reference and geometry, which with a table is not required,

View solution in original post

BharatKale
New Contributor

Thank you Lance for looking into the issue. Your suggestion has fixed my issue.

My understanding about the CLSID here is that it can be any GUID value as long as it's unique. Now I got it right and it's a constant value based on the type whether it's a table or a feature class.

Also, I was confused mainly because the same table.xml which is not working with APIV1.4, is working perfectly fine (with the CLSID value as {52353152-891A-11D0-BEC6-00805F7C4268}) with APIV1.3.

0 Kudos