Qdabra Database Accelerator

Re: Specify Starting DocID, or Import Existing Database?

MediaPro — Wed, 17 Oct 2012 20:31:32 GMT

That makes sense. Thank you so much for the quick replies; I really appreciate it!

Re: Specify Starting DocID, or Import Existing Database?

Hilary Stoupa — Wed, 17 Oct 2012 00:58:42 GMT

Yes, it does. So you'd be able to copy your existing data from your existing tables into different worksheets in an Excel workbook and use the tool to generate new XML (which would then submit to your new data tables that you have set your DBXL document type up to save data to). Does that make sense?

Re: Specify Starting DocID, or Import Existing Database?

MediaPro — Tue, 16 Oct 2012 23:32:31 GMT

If I were to use the XLS to XML tool to resubmit my data, would it support child tables? I have a main Contracts table, one child table with repeating line item data, and another child table with repeating billing data.

Re: Specify Starting DocID, or Import Existing Database?

Hilary Stoupa — Tue, 16 Oct 2012 23:02:24 GMT

Hi -

Not to seem like a car salesman adding on the extras, but I'd probably encourage you to use our XLS to XML tool to create XML forms for all your existing data and submt to DBXL using the DBXL web services. Then your new XML would each get a new DocId.

Here's a blog post that talks about limitations with DBXL and existing data.

Specify Starting DocID, or Import Existing Database?

MediaPro — Tue, 16 Oct 2012 22:16:22 GMT

I am using a trial of DBXL 2.6. I am working on recreating an existing form using the DBXL web services. I was planning on using the DocID as the Primary Key for my SQL tables. Is there a way to specify the starting or next DocID? I have a lot of existing data that starts at 1000 for the ID. I also saw a post about importing data into DBXL. I have a table and two sub-tables. Would it be better to just import the existing data? If so, how would you recommend doing so?

Thank you,

Joe