OK - apparently this project is "overshadowed" by some bad vibes. "TUSC". Now, don't know what the hell that is and haven't even done a search for it because it's of NO concern of mine. And if it's a DELPHI vs. C/C++ situation, then I won't get into that "this development situation is better than that development situation."

You have a fully functional situation here. Two .exe's that for now function while I work on integrating them into ONE. The client has an exit procedure problem that will give you an access errot - but won't hurt your system.

To state again - currently you can define a client (both local and remote), start MULTIPLE databases in the explorer module (with aliases) and use SQL. Once tables are defined - you can add, delete - well all those database things.

Before I encapsulate it into a .dll - I released the .exe to determine if you would like to see it go further. I have created a "wizard's" system for "noobs" to create databases and have an "alpha" of the .dll and a .wdl and a test level to show how to incorporate it.

But no one seems to be interested. If this is the case, I will stop development for the community here and use it for private projects and outsource it for other indie engines. Is anyone really interested in this or am I just wasting my time in the shadow of "TUSC" and it's bad reputation?

With all the whining and complaining that "we don't have tools", I would think the community would try to embrace this, download and evaluate it and then - at least say, "you're heading down the wrong path".

Have you stopped and thought what this can do ... static and dynamic data creation/storing? Instead of several .dll's - you could store (with proper dynamic queries) your "HIGH SCORES". You could store your items and inventory. For RPG's - your npc's responses. Whether he/she is interactive or not (in a BOOLEAN) and if so ... can they give quests. Do they offer rewards?

As structure now - DELLA allows you to create these databases. I purposely went ONE step at a time - first the actual engine so you see how it works - giving you the opportunity to give input into the ACTUAL ENGINE - the interface for that before I encapsulated it into a6. But yet - no one seems interested in the development process, before it becomes a "crappy" tool just thrown together.

The way a good software tool should be developed - input at every step.

Should I - or should I not continue this for this community. I am already using it in my project(s) and have people that want it for their. I held off release to them. You want it or not.

And don't compare this with anything else that might have been developed. Download the damn thing - play with it and give me some REAL feedback.