Pervasive Community Site
Community Forum (formally DEVTALK) – Join the ever- growing Pervasive community in a lively, interactive e-nvironment where users can come together and discuss their choice of topics on Pervasive-based products. Participants include Developers, Resellers, System Integrators, and End User and Pervasive team members.
Component Zone – Download the latest utilities and tools posted by third-party vendors. The Zone is your quick stop for getting the latest tools our partners have to offer.
Thanks for information both of you. Bill: I did it my self. It was actually quite nice to get hands dirty on some low level api, haven't been doing that for a long time. We have own ddf builder for file, field and index manipulation (because of we still have some old Smitware based datatypes in use) and it was logical to put fix there. We have plenty...
Well THAT just seems silly to me. This sounds like a job for.....Tool Man! mikakoistinen: Can you send me your DDF's via private message? I'll see if I can build a conversion tool. I can imagine a lot of developers rolling out PSQL v12 internally, but still with customers on PSQLv11, running into this as time goes on.
This is expected behavior. Going older to newer (Stored Procedures, Triggers, Views, etc created in v11 moved to v12) works just fine, just not the other way around. The only workaround I can think of is to copy the text of the Stored Procedure from v12 and paste it into v11. This will create them with v11 compatibility.
If I edit stored procedure in v12 pcc, it seems convert it to utf-8 or something. If I try to open it with v11 there are three extra characters in it and calling it in v11 will cause "general error". Before anyone asks to be more specific with error (like I did while talking to our distributor), I say that error is for example "[Pervasive...
Just a note about the configuration of the PSQL firewall rules during the PSQL installation... Note that the PSQL firewall rules are only configured in the manner shown in your screen shot if the ACTIVE Windows Firewall profile is set to PUBLIC at the time the PSQL installation is run. The PSQL installation always ADDS the firewall rules to all three...