Thanks for your reply David I'm looking for something more concrete then ODBC - That's certainly what I'm going to use since the application is going to be cross platform (and the database is an MS SQL Server). But how would you create the classes responsible for holding the database-data which the UI uses?

Jan Sommer wrote: Do you know of any documents that describe the Doc/View architecture in a way that's not MFC/wxWidgets-specific? I don't know of any specific documents, but I would expect that MSDN contains a lot of the information you need to utilize the Doc/View architecture, including sample code.

Rob Graham wrote: You have no idea what you are talking about. :wtf: I Love T-SQL "Don't torture yourself,let the life to do it for you." If my post helps you kindly save my time by voting my post.

Always at your service... :) Regards Thomas www.thomas-weller.de Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Programmer - an organism that turns coffee into software.

It doesn't really make any difference, classes are easier to deal with though. I tend to use structs for all my values (structs are value types) and classes for the final objects that use those values. I personally find this makes more sense, but unless you're 100% sure you're handling value types correctly - use classes. Dave BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn) Expect everything to be hard and then enjoy the things that come easy. (code-frog)

=! is not an assignment operator int some_variable; some_variable =! some_variable; means assigning (! some_variable) to some_variable ;)

Rajesh R Subramanian wrote: You beat me to it, you addict. Shhhhhhhhhh, don't spread such rumors. ;) If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke

The writer.optimize() part certainly took alot of time. I removed it and placed it after the while odreader.read, and that saved me 1/3 of the time it took to index the db. But it still isn't fast enough. Currently i'm indexing the DB and when i check the taskmanager it says something like: Process: IndexService.exe, CPU: 00 (sometimes 01) and memory: between 100.000 and 800.000 Why is it taking up all the memory and not using the CPU? The indexing program is soon going to run on a server with a bit more ram. I hope that will speed up things a little. Will it be any faster if i somehow convinced the IT-department to switch to MSSQL?

You're right about noone is going to debug all that code. Guess i was a little naive to believe in that. I've found another control that does pretty much the same and in vb.net. But thanks for trying to help. Maybe i should try out c# some day :)