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.
Howdy, I'm trying to figure out how to format an entity framework connection string that uses an Entity Framework project. So my DB project applicationDB is an entity frameworks project and I have another console project that is attempting to use the applicationDB project. I don't want to put the whole entity frameworks connection string in...
Since there is not actually a defect opened yet, I don't have a way to get you the DDFs and data. Unless you can instruct me as to how to get them to you for analysis.
We always have several characters of FILLER defined at the end of our files so we don't always have to modify our COBOL/Btrieve I/O modules for a table modification. As I replied to Shelley Gu, if I add a 750 character column it all works great, the record length is at 4960. If I go to 1000 characters then I start getting all kinds of od errors...
It looks like you have pc_filler_1 as the last column, and your new CHAR(750) is second to last. I think it may be best if you zip up your DDFs and datafile and submit them via DefectFYI. We need your files to test this. Also, can you answer these questions? What errors do you get if you try to access the Btrieve file via Function Executor? What version...
I am adding the column at the end of the table now. If I add a CHAR(750) column to the end, then all is well. If however I add CHAR(1000) then I begin to see errors in other table open/access actions. Doesn't make sense. See my replies showing the table after the add of the column.