This is a request for the guru's here and our favorite administrator, Pat Phelan. Many of us novice users are making some critical mistakes early on in our project. These mistakes do not become evident until the project gets much larger in size. As a recent example of something wrong I did was using Recordsets to store massive amounts of data. Early on, while the data set was much smaller, it worked fine but when I finally received the whole three years volume of data, things went askew and I had no idea why.
James Tubbritt pointed out that Recordsets were never designed to hold that much data yet there was nothing in the Brilliant Database User's Manual that makes any mention of this. After this discovery was made, ferslash pointed out that this answer possibly solved some of his previous issues. Because this issue was unknown to me (and apparently others), it necessitated redoing volumes of scripting. James undoubtedly knew the solution because he, too, found out the hard way.
Because of the absence of actual help from Brilliant Database, if there was a small repository of 'best practices' here on dBforums it could get folks started in the right direction.. and save countless hours of unnecessary frustration and possibly cause the community to grow in size.
So, I am going to beg our administrator Pat to start a 'sticky' thread that contains just 'best practices' and I request that James write a short narrative about avoiding the usage of Recordsets to hold large volumes of data for the initial post. Why should we all have to repeat the same mistakes that those more 'seasoned' and experienced individuals have already made?
James Tubbritt pointed out that Recordsets were never designed to hold that much data yet there was nothing in the Brilliant Database User's Manual that makes any mention of this. After this discovery was made, ferslash pointed out that this answer possibly solved some of his previous issues. Because this issue was unknown to me (and apparently others), it necessitated redoing volumes of scripting. James undoubtedly knew the solution because he, too, found out the hard way.
Because of the absence of actual help from Brilliant Database, if there was a small repository of 'best practices' here on dBforums it could get folks started in the right direction.. and save countless hours of unnecessary frustration and possibly cause the community to grow in size.
So, I am going to beg our administrator Pat to start a 'sticky' thread that contains just 'best practices' and I request that James write a short narrative about avoiding the usage of Recordsets to hold large volumes of data for the initial post. Why should we all have to repeat the same mistakes that those more 'seasoned' and experienced individuals have already made?