Download: good morning I have a database and a table with 250,000 records I need to export that table is a selection of recording and I do it for the function in the table DataEase Data Export and select the options button Selected Records and therefore selected the Range option but when I digitarle the initial rank and the final rank will not let me enter more than five digits Example when I go to type only lets me write 250 000 25 000 both in the initial range in the final rank Thank you and sent this comment to expand the length of the fields and exports can be made from this option as it is very useful and easy to do Thanks for your feedback

Download: Good evening from London Wilmer. I have one good and one bad news for you. This is fixed in DataEase 8. For fun I created a database with 11.000.000 records, and export the lot. Worked a breeze, but Write struggled with opening the document ;-). The bad news is that we are not in charge of DataEase 7.x, so any bug fixes etc prior to DataEase 8, you will need to discuss with Sapphire/DIL (www.sapphiregroup.com). If you cannot wait till DataEase 8 is released, you can try to use the method described in the Sample: DQL Export in 7.2 This is a much better way of doing it if you want to do it automatically and flexibly. Define temp "expo" number . Define temp "telle" number . For All Companies2 with CompanyName between getarray(1) to getarray(2) ; telle := telle +1 . list records CompanyName in order; pUKMarketingDatabaseID ; Address ; Address2 ; Locality ; Field 7 ; Postcode ; fRegionID ; PremiseType ; NoOfEmployees ; fBusinessTypeID ; SICCode ; FinancialYearEnd ; Turnover ; ProfitBeforeTax ; NetWorth ; TelephoneNumber ; WebsiteAddress ; ContactFullName ; ContactJobTitle ; EmailAddresses ; fCountyID ; getarray(1) ; getarray(2). if telle = 1 then Expo := DataExport ("DQLEXP.DBE") . exit end In 7.2 we fixed the DataExport() function so you could include a export definition. The method shown in the DQL Export example is exploiting the actual functionality of DataEase, not the one emulated in the DQL implementation done in DFW. DataEase create a multiview i.e a dynamic joined view for any query. This view contain all the columns and data for the query. Amy FRM, Report etc is reverse engineered from an expected dynamic Multiview that is created when you search. I.e the multiview just end up containing all the columns represented in a form, but it is not limited to it. The DQL implementation in DFW is basically "ruining" the real functionality in the multiview, because they tried to make it "behave" the same way it did in DFD. What we ended up with was one that got the worst from both worlds. The reason you cannot run an export the same way as an import definition from anywhere, is due to the multiview. An export definition need a queried multiview to export, and in DFW this can only be done from the current active document. A DBE doesn't export a Table or a Form, it exports the current multiview, so that is why the only thing stored in it is field names. Another limit is that you can only add existing field names to a DBE, so you need to create it on a multiview that contain all the columns you want to export. The good bit however, is that you can use it anywhere later, and it will export the columns that exist in both the Multiview and the DBE. So what I do in the example is as follows: I create the DQL with a list record of all the fields I want to export. I then compile it and go to the DQL body. Here I "export" i.e. I create a DBE based on the mutltiview created by the DQL. I then go back to the DQL, and add this: if telle = 1 then Expo := DataExport ("DQLEXP.DBE") . exit end Now the DQL will use the built in Export functionality that exports directly from the multiview, rather than the slow and cumbersome EXPORT TO. The reason I exit after I have exported it, is that this way I don't have to wait for the DQL to finish, because it already is! In the meaningless DQL implementation done in DFW, the DQL actually run through the data twice. One the modern and hyper effective real DataEase way, and then again in single step to do all the DFD emulation stuff. So we can't be bothered with the last bit so we simply chop it's leg off. If you don't understand a word of what I have said above, don't worry. The example is in the DataEase 7.2 samples, and by studying it, you will get what I mean.

Download: The best way of insuring a good product, it to have more than one way of doing the "same"...it is called redundancy. To be honest, something DFW has been really bad at. Our main goal for 8, is to expand it with new and alternative ways of doing the "job". Fixing the current way, like the horrible DQL implementations is now impossible. Why? Because a lot of people use it, and they have tweaked, turned and stretched it to try to get it to do what they want. How can we change it and insure that it work the same "cr....y" way? No we leave it alone, and implement alternatives parallel with it. That lead us onto why we are posting here... Yesterday we offered a solution to exporting intervals using DQL and the built in DataExport() function. This was as a response to a limitation in 7.2, where one can only export intervals up to 99.999. Now that we have offered an alternative, and in our mind better way from a programmatic viewpoint, we can't leave the real issue unsolved. It just smell too much of how DataEase used to be. Today we spent a little time, implementing the fix in 7.2. It is not thoroughly tested, and we neither can or want to publish a full release of 7.2, but for those of you that know your file explorer, it is rather simple to implement the fix. 1. Download this file.http://www.dataease.com/static/files/deresdlg.dll 2. Close DataEase 7.2 and take a copy of the file with the same name in your DataEase program catalogue. 3. Copy this file to the DataEase program catalogue. 4. Restart DataEase 7.2 and try to export an interval. Also check that everything else works and looks right. Enjoy!