Batch loading VFP9 data into Lianja via scripting

[chrisg@pso.siu.edu]

Create a link to the App Builder or SQL Server directory?

mklink /J C:\Lianja\data C:\Lianja\cloudserver\tenants\public\data

or

mklink /J C:\Lianja\cloudserver\tenants\public\data C:\Lianja\data

What will SQL server do while App Builder is running and has opened the database exclusively?

Should the SQL Server service be stopped while in development mode?

Just need to know if I should script the starting and stopping of the service.

[barrymavin]

Hi Chris,

Lianja purposely lets you build Apps with a local copy of the data and then publish it.

The App Builder requires exclusive access to the database and its tables.

Lianja SQL Server (as you know already) accesses the live database i.e. the ones you deploy.

If you have a database open in the App Builder and you create a symbolic link *from* c:\lianja\data to c:\lianja\cloudserver\tenants\public\data (either way makes no difference) then I can see a few issues.

1. When you upgrade to new versions of Lianja
2. If the database is open in the App Builder then SQL server will not be able to access it as it is opened for exclusive access

There are few things you can do.

1. Always push your data into a "staging" database and then in a script copy the data over into the development directory
2. Stop SQL server while you are developing and restart it when you want the new data.

Basically you can't have SQL server and the App builder access the same data at the same time... unless the tables are all Virtual Tables that are defined in your database (App Builder directory) that use ODBC to access the *real* data via the Lianja SQL Server. The way you have described about zapping and overwriting tables will probably not work doing this also.

So. It would be better to have a staging area or just allow refreshing the databases from VFP when no App Builder has them open. In fact SQL server will just fail to open the database and will automatically succeed when the App Builder is closed.