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.

What's New

  • Re: Support for records > 64 KiB

    No -- 64K is the maximum buffer size available for communications. In fact, there is also some overhead, so you won't be able to get all the way to 64K, even. I recommend making your code flexible enough to change the maximum request size easily, if needed. For example, the older NetWare engine used to have a limit of around 57000 bytes for the...
    Posted to General (Forum) by BtrieveBill on 07-29-2014
  • Support for records > 64 KiB

    Hi, I want to build support for records > 64 KiB into my apps. My apps use native BTRV and SQL access as well. For native access: Before I program a solution with GetDirect/Chunk and UpdateChunk to read/update records > 64 KB I'd like to know whether there is a better solution. In my apps I support a data buffer length > 64 KiB I detected...
    Posted to General (Forum) by Werner on 07-29-2014
  • Re: ODBC error using time fields in parameters v11.31

    I tried it with another table and get same error. It has no problem displaying a time field. It works OK when a set value is used in the filter condition. It just does not like having them as a parameter in the query. I'm guessing parameters are all strings and the ODBC client attempts to convert the entered value into a time to filter by and is...
    Posted to General (Forum) by adam.jackson on 07-29-2014
  • Re: What is "connection pooling"?

    Thank you all
    Posted to General (Forum) by Cholotron on 07-28-2014
  • Re: What is "connection pooling"?

    I am not aware of any provider issues regarding connection pooling. Are you seeing connection time out or session timeout in the pvsw.log?. Is Psql "park" turned on? You can control how many connections you want in the connection pool and how long the connections should stay open. Application can also use clearpool to clear the existing pool...
    Posted to General (Forum) by jvarughe on 07-28-2014