This is my first time using filemaker and I'm in the process of converting a client's filemaker project to a webapp. Currently, I am trying to export the current data so that I can put it in a database.
I've found that tables don't appear for export unless they appear in the "Relationships" graph, and I've found that I can export the data using the "Export Records" script command.
This all works fine except that I can't seem to export all the records. In the database manager, one of the tables reports that it has 596 records, but when I export it I only get 119 records. The same is true for all other tables I've tried, they report more than 119 records, but the exported data only has 119.
Any ideas or help is welcome
edit
More progress, it seems the script runs in the context of the current layout, so the number of records is related to the number of results in the current layout. Is there a way to automate creating layouts for tables that don't have them so that I can export all the data for each table?
The concept you were missing was the "found set". FileMaker exports the currently found records in the current layout. You can create a script that grabs the names of the layouts within the file, sticks into a variable, goes to each layout in turn, performs a Show All Records, and then runs an open ended export. However, I'm wondering how many base tables there actually are?
As to creating layouts - nope, there's no programmatic way. However, it is possible to use an external key macro type app (QuicKeys?) to run through the create layout dialog and choose a new table each time.
Related
I am creating a business app to manage the inventory of a mid-sized shoe company.
I already have a database created with PostgreSQL. I would now be able to connect it to Odoo 9 to develop applications.
How can I do that?
You can't just use your existing data directly with odoo
But Odoo makes it easy to use existing data from existing applications and databases with it's flexible import system. in which data is imported to it via csv files, you can import any data you can possibly think of, you just have to know the right format of data that odoo is expecting and the required fields you have to provide
Every model in Odoo even custom built modules can have data imported into them
If you want to import data just click on the listview of any model and you should see an import link beside the create button, from there you can carry on, there's even a FAQ there which you can read if you need to find out more about the import system.
As for knowing the required columns that have to be present when you're importing, Just create sample data and save it, Then
Go to the listview
Tick the check-box beside the record name to select it
Now click on the more button you should see an export option
From there you can pick the fields you want to export, the required fields will highlighted in blue
There are other ways of re-using existing data with odoo (You can write to the database directly...but this is not recommended as several constraints would not be checked and you can end up messing the database up) or you can use xmlrpc or jsonrpc which is going to be time consuming
Using the import functionality is the best and the easiest way.
I have a working Drupal site that i need to replicate on another server, so that the replicated version doesn't contain custom site information like users data or specific article published on the main site.
So i did a selective dump of the main db, and re-imported in the replicated site. In the specific case of the "node" table, I imported only nodes of the type "page". Now, all went well. The main functions of the site are working, but i have a problem with pages throwing an error "The requested page "/node/page_number" could not be found." with ALL the basic node pages. I can see only views and the front page.
Probably i'm not dumping some information needed by Drupal to display the node. So the question is: where i can find info about basic nodes? I thought porting the table "node" and "node_access" was pretty enough, but really it isn't.
The problem is that node table stores only basic information.
I think you did not imported node_revision table as well.
Even if you do, dumping tables and re-importing only specific data into another database breaks their connections, by resetting id columns and missing extra data provided by fields and other custom modules.
Consider using Import/Export modules, comparison of which you can find Comparison of Content and User Import and Export Modules
Consider the data_export_import module.
What I like about data_export_import is that it is an all-in-one module (for export AND import of data. Whereas as with some other solutions, the import and export stages are done by separate modules, which could mean that extra work is needed ensuring compatibility of the export with the import.)
Is there a way to automatically generate SSIS packages? I need to create a lot of SSIS packages that just erase data from one table and import data from a text file. The file name matches table name and the column headers are in the first line of the file.
For more detailed information:
I am working on a project in which I have to separate two systems that are currently coupled (one system has direct access to the other's database). After the modifications, one system will provide data through txt files to be loaded in the other database.
We have to use SSIS to load data into the database from the text files.
The text files will be provided in CSV format with column headers in the first line.
The tables from both databases have matching column names, and all we need to do is clear the table and load data from the files.
I have more than one hundred tables with different number of columns. Do I need to create each package manually?
I'm familiar with 2 free options.
EzAPI might be a good place if you're a .NET heavy shop or just really want to geek out with the API. This approach allows you to control the pretty much the entire package generation but at the cost of coding time. I find EzAPI generally easier than working with the base COM/.NET libraries for SSIS.
Biml is an interesting beast. Varigence will be happy to sell you a license to Mist but it's not needed. All you would need is BIDSHelper and then browse through BimlScript and look for a recipe that approximates your needs. Once you have that, click the context sensitive menu button in BIDSHelper and whoosh, it generates packages.
I did this just using vb, I passed in the table names as a command parameter and used vb to generate the insert and clear, worked a charm... I can try and dig it out tomorrow when I'm back in the office but it was pretty simple. There didn't seem to be any other way to say "just get x and export it", "just take y and import it into z" so vb it had to be. In fact come to think of it I think I actually used a small xml file to pass the table info for export and then determined the table name for import from the csv file name. To be clear, this was only one package but it could dynamically choose the number of imports/exports it did. Further clarification this was vb within ssis as a processing step
I am enhancing and fixing the forms/queries/VBcode etc. for an access 2007 database. The current version is being actively used and when I am done with my changes I need to transfer in my changes without disrupting the data stored in the tables already in the running mdb.
I'm not entirely sure how to handle the "merge" when the time comes. As an experiment I have a local backup copy of the version I started working on and used the import external Access data option. This imported the new forms, queries, vb, etc. But the only hang up is that the switchboard form isn't the new. Switchboard forms of course are guided by the switchboard manager but I was hoping that all that logic is held inside the form itself somehow. It seems this is not the case. After the import there is a new form of the same name with a number after it as expected, and the correct create/modify date. But when open it looks exactly the same as the old switchboard.
Any ideas?
It sounds to me as if you have both the data and the forms etc in the one database. This is not a good idea at all and if you are updating, it is the ideal time to correct the problem. If you split the database, any updates to forms and code can be simply copied to the user without worrying about the data. You will find some notes here: http://office.microsoft.com/en-us/access-help/split-an-access-database-HA010342026.aspx
The Access switchboard manager uses a table named Switchboard Items to dynamically populate switchboard form pages. You will need to transfer the updated version of that table to make your revised switchboard pages available in the other project.
I'm kind of new to Access. I've got some experience working with integrating MySQL and Oracle with PHP to create web-based database search engines, but I am having difficulty understanding certain concepts with Access.
I've got a small database with around 200 entries with 20 fields each. I've written a form to search it by using VBA to run an SQL query against the database and displays the results in datasheet mode to a different form (is this the standard way of doing this, or is there a better way?)
I want to be able to add a button to export those results to excel (or csv or tab or whatever, it doesn't really matter). However, I'm not sure how to do this with the form results. Its easy with an entire database, but I can't find documentation on how to do this. Is there a way to do this? Or am I doing this wrong?
If at all required, I can provide more details.
You said "I've written a form to search it by using VBA to run an SQL query against the database and displays the results in datasheet mode to a different form".
If you mean an actual form in datasheet view, you can export that form's data to Excel with the DoCmd.OutputTo method.
DoCmd.OutputTo acOutputForm, "frmResults", acFormatXLS, _
"C:\SomeFolder\ExportedResults.xls"
However, if you're opening a query in datasheet view, rather than an actual form, you can export the query's result set.
DoCmd.OutputTo acOutputQuery, "qryResults", acFormatXLS, _
"C:\SomeFolder\ExportedResults.xls"
You can choose a different OutputFormat instead of Excel if you wish. Look at Access' Help topic for the OutputTo method to see the available choices.