Maelstrom wrote:Just a question, How would you people like it if this was made into a .EXE that incorporates an Access database? That would solve alot of problems. Ofcourse, it would also raise alot of new ones, but we can deal with them as they come.
Advantages of Access:
No ... limit.
...
Yes, Access is a proper database setting. Relations and stuff.
Think just a little further and you'll end up thinking of making the exact same thing as i've been wanting to make.
My idea was to create a DataBase in MySql for handling Unit Packs. Relational databases are very usefull for that since we have quite a few relations in the unit packs we currently have. For example, we have the unit's weapons which are related to a «table» of weapons in a many-to-many relationship.

The table on the right will store info as:
Unit of Id 1 has a weapon of Id 1.
Unit of Id 1 has a weapon of Id 2.
Unit of Id 1 has a weapon of Id 3.
Unit of Id 2 has a weapon of Id 1.
So, we don't have to always create a new weapon for the unit if it is the same, we can just reuse them for other units. Also, we have no real DataBase limits to how many weapons (associations of Unit-Weapon) we can have per unit. All this stuff is very powerfull.
Also, using SQL (structured query language), we can make powerfull queries (among other things). For example:
Code: Select all
SELECT * from TableUnits where name like '%commander%'
This simple one will select all fields from that table where, in the name field, contains the string 'commander'.
Code: Select all
SELECT TableUnits.* from TableUnits inner join TableWeaponsUnits on TableUnits.IdUnits = TableWeaponsUnits.TableUnits_IdUnits where TableWeaponsUnits.TableWeapons_IdWeapons= 5
This more complex query, will select all fields from the table TableUnits which are associated with a weapon of id=5. Very usefull if, for example, you want to see all units that are using the emg weapon.
I've been having a few issues with the «project», though.
1- Lack of time for it.
2- I'm not entirely sure what relations the new unit format will have, as wel as fields.
3- All that is pretty much useless if i don't offer along with it, some GUI way of editing the database. I can't expect people to have a tool for connecting to it and to know enough SQL to make they're own SQL comands. But i wanted to make it so that in a server-client way so we could have teams of people responsible for testing and changing. This of course implicates autentication to prevent ill intentioned people from ruining the database. If i make a C# program, it can't handle it's own autentication because anyone could just change the program to bypass the autentication. It must be made server side. I'm not entirely sure how to do that and it's hard to do such intermediate tool. That can be properly made through a web server. The problem is, i don't know how to make that in PHP. If only i knew how to work in PHP... I do know how to make it in ASP.NET but, fnordia's server is apache in windows (meaning no asp.net) and i don't know where such ASP.NET enabled server could be found to host such a thing.
Access, unlike Excel, is a proper database. You'll be able to design databases with relationships, make SQL queries to it and everything. I can even help you in that, if your father won't be able to. I'm a moderatly good database designer and an average SQL scripter.
However, it adds more dificulties. So , it isn't just better. The dificulties you'll have added might, still, make Excel a better tool for you. Or not.
If you really decide to go for Access, welcome to the real DataBase world and may the gods of OpenSource be with you.