Lost your Activation Code / License Key?
Enter your email address into the form below to have your License Key re-sent to you. Please ensure that the email entered is the one used when you registered your software. If you encounter any problems, don't hesitate to contact us at .
If your junk mail filters are turned on, then have a look at your junk mail folder as well. You might find us in there if we're missing from your inbox.
Daeta FAQs
What SQL data types are supported?
Daeta works with most standard JDBC types, and certain non-JDBC-standard types as well. Precisely what functionality is available for a given type depends upon which Widget you use to view/edit a datafield of that type, and the JDBC driver in use (e.g. PostgreSQL's geometric types are viewable and editable using the Field Widget, with the appropriate JDBC driver).
How do I view and edit dates, time and timestamps?
You can use the Label and Field Widgets to view (and in the case of the Field Widget, edit) those particular types using the following formats:
Dates: 'yyyy-mm-dd' (e.g. '2008-07-23' would be the 23rd of July 2008)
Time: 'hh:mm:ss' (e.g. '08:10:00' would be 10 minutes past 8 A.M.)
Timestamp: 'yyyy-mm-dd hh:mm:ss.fffffffff' (e.g. '2008-07-23 08:10:00.0' would be 10 minutes past 8 A.M. on the 23rd of July 2008, exactly)
My connection to a remote database server keeps timing out, what do I do?
Select 'Connection >> Keep Alive' from Daeta's main menu, and Daeta will attempt to keep your connection alive. Ideally, speak with your database server administrator and request a longer timeout period.
When accessing records through PostgreSQL, I get error messages telling me 'no primary key found for table'. What does this mean?
This means that the PostgreSQL JDBC driver cannot uniquely identify the records in your record set (and hence, cannot properly navigate through them or pick out a specific record to refresh/update) because a primary key column has not been designated in the table.
Primary key columns contain unique identifiers (usually an integer) to ensure each record can be uniquely referenced - it is considered good practice to have a primary key column defined for any database table you create.
I can't always insert/delete records from my record set. Why?
If your record set consists of joins between tables (i.e. columns taken from multiple tables and combined into a single record set) it may not be possible to insert/delete records into/from that record set, due to missing fields and for other reasons.
Support for insertion/deletion with joined tables depends on your JDBC driver, and requires carefully structuring your query to ensure all the tables in the join have valid values provided for all their fields during insertion. In general, it is best to avoid inserting into / deleting from joined tables.