Forum > Packages and Libraries
Postgres, ZEOS and Visual PlanIt - unable to create a table
calebs:
hello all again. creating manually the tables seem to work (at begining) and the components initializes.
Dropped a vpview, vpmonthview,vptasklist, a zconnection, a vpzeosdatastore, and vpcontrol link.
created the database with manually sql, then it generates a record on resources table.
the problem appears when i try to add some event in vpdayview, double click on some day/hour then fill in the window of untitled event with some description and anything else and click on ok then gives me an sql error.
I'll attach the sql i ve used to create the table on db.
andersonscinfo:
Hello,
The issue you're experiencing is likely due to differences between the expected table structure by Visual PlanIt components and the manually created tables. When you create tables manually, it's crucial to ensure that all fields, constraints, indexes, and triggers match exactly what the components expect.
Here are some steps to troubleshoot:
1. **Compare Table Structure**: Check if the table structure (field names, types, sizes, constraints) matches what Visual PlanIt expects. Often, components have specific requirements for field names and types.
2. **Check Primary Keys and Indexes**: Ensure all required primary keys and indexes are properly defined. Missing indexes can cause insertion problems.
3. **Auto-Increment Fields**: If there are ID fields that should auto-increment, make sure the sequence or auto-increment property is correctly set up in PostgreSQL.
4. **Triggers and Constraints**: Some components rely on database triggers or specific constraints to work properly. Check if these were created.
5. **ZEOS Component Configuration**: Verify that your ZConnection and VPZEOSDataStore components are properly configured with correct connection parameters and that they're compatible with PostgreSQL version you're using.
6. **Debug the SQL Error**: Enable detailed logging in your application to see the exact SQL statement that's causing the error. This will give you a precise idea of what's going wrong.
Could you share the SQL error message you're getting? That would help pinpoint the exact issue.
Also, the SQL script you used to create the tables would be helpful to compare against the expected structure.
Att.
calebs:
--- Quote from: andersonscinfo on January 18, 2026, 11:01:09 pm ---Hello,
The issue you're experiencing is likely due to differences between the expected table structure by Visual PlanIt components and the manually created tables. When you create tables manually, it's crucial to ensure that all fields, constraints, indexes, and triggers match exactly what the components expect.
Here are some steps to troubleshoot:
1. **Compare Table Structure**: Check if the table structure (field names, types, sizes, constraints) matches what Visual PlanIt expects. Often, components have specific requirements for field names and types.
2. **Check Primary Keys and Indexes**: Ensure all required primary keys and indexes are properly defined. Missing indexes can cause insertion problems.
3. **Auto-Increment Fields**: If there are ID fields that should auto-increment, make sure the sequence or auto-increment property is correctly set up in PostgreSQL.
4. **Triggers and Constraints**: Some components rely on database triggers or specific constraints to work properly. Check if these were created.
5. **ZEOS Component Configuration**: Verify that your ZConnection and VPZEOSDataStore components are properly configured with correct connection parameters and that they're compatible with PostgreSQL version you're using.
6. **Debug the SQL Error**: Enable detailed logging in your application to see the exact SQL statement that's causing the error. This will give you a precise idea of what's going wrong.
Could you share the SQL error message you're getting? That would help pinpoint the exact issue.
Also, the SQL script you used to create the tables would be helpful to compare against the expected structure.
Att.
--- End quote ---
hi, the error is attached on the two snapshots in my post (had to split it because its too long and windows capture can't handle 2 monitors). I had to create manually the databases because it won't auto create them on first online (it always gives an error) the script for create it its also attached on my post. The script to create database and tables i made it taking the official info that i've found for the component
Thaddy:
What I am missing is this: table creation manually succeeds.
Tables need a database/datastore.
Looks like that is missing/ not set when you use the components, so create that first: only then you can add and create tables.
Navigation
[0] Message Index
[*] Previous page