DBXL Help - InfoPath Dev
in

InfoPath Dev

DBXL Help

Last post 09-22-2010 06:33 AM by ErnestoM. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 09-21-2010 07:02 AM

    DBXL Help

    Hi ,

     

     We have purchased the Basic version of DBXL  Database Accelerator.

     

    We have been able to successfully install DBXL in our  production server.

     

    The DBXL is installed on the same server where SharePoint is installed and the SQL instance used by DBXL is on another machine.

     

    For now, we have only one XSN that we want to shed the data to SQL Server using DBXL.

     

    We plan to set up and Test everything in the Development Server before we move it to the Production.

     

    My question is:

     How can I use  XSN’s as a test document types in the development server?

    Is there a way I can use a different instance of SQL in Development server without affecting the live database?

     

    Please advice.

     

  • 09-22-2010 06:33 AM In reply to

     If I have understood the scenario correctly, you have one installation of DBXL and want to use it as both Dev and Production.

    To accomplish this, you’ll need two doctypes and two sets of tables. So let’s begin with the DEV tables. Let’s assume your DEV document type will map data to these three tables.

    •    DEVTable1
    •    DEVTable2
    •    DEVTable3

    In the database tab for the DEV document type, you can control where the data gets shredded, simply select the specific tables (the DEV tables).

    Once developed and tested, you want to create your “production” document type and tables. You can create tables with the same structure but remove the DEV prefix.

    To create the production document type, click EDIT for the DEV document type. You’ll see a Save As button at the top. This will allow you to create a new document type, with the same XSN and database mapping, but with a different name.

    Give the doctype a new name, and clik Save. This new doctype (“production”) will contain the same database mapping, though you’ll need to update the table names due to the removal of the DEV prefix in SQL.

    You can control where the xml data is mapped by changing the data connection string. So you could have two document types, with the same xsn and the same mapping, but using two different connection strings. One will be dev/test and the other can be production.

    Hopefully I’ve understood the question… let us know if you have any questions on this.

    Ernesto Machado
    Qdabra® Software/ InfoPathDev.com
    The InfoPath Experts – Streamline data gathering to turn process into knowledge.™


Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.