Stano

I did it via csv files. There were/are only 16 tables. It is very easy to treat the character there.

Are you considering a normal DB? The paradox is 30 years old and brings nothing but trouble. Do you want to worry about it all the time? I'm converting, I'm robbing one program with Paradox to D11. The first thing was throwing away Paradox and exporting/importing its data to a relational DB. Firebird. It Connected and Active needs to go from OnCreate out. You've already figured that out. PS: I'm using my own solution. I'm only inspired by the content of the individual forms and the logic of the program.

Aha. My poor English + not paying attention/not noticing. Thanks!

I wanted to report it. I didn't find that option! Personally, I think that should be a possibility.

No way! I tried it once. I didn't get along with the date at all. FB suits me just fine. In my case, the connection isn't that big of a deal. I also bought tools to go with FB. It would be a shame to throw them away.

I forgot to write that in my program this is the Embedded version.

That's exactly how I understand it. How can it be done?

Project FootMan.exe raised exception class EIBNativeException with message '[FireDAC][Phys][FB]I/O error during "CreateFile (open)" operation for file "D:\DOKUMENTY\DELPHI XE7\FOOTMAN\DATA\FOOTMAN.FDB" Error while trying to open file The process cannot access the file because it is being used by another process. '. As you can see, it doesn't work for me. Do I have something wrong?

As I have in my signature, I am a layman. Delphi is more of a hobby. When I looked at it, I didn't see anything interesting to me there. Among other things, because I have: MMX CnPack FixInhsight Pascal Analyzer ... They provide me with more than I need. I don't need it for more complex stuff - I don't have it and couldn't handle it. But I struggle with that problem from time to time. I have to switch it all the time. Active at design time and inactive at compile time.

Did I install it just for that?

I do that too. The problem is if I use TFDTabale and I want to generate a list of table fields. In that case the connection must be active. It's annoying. In a large project this must cause problems.

I think from D11. It's alerted me a couple of times to a fix.

I don't work with Stringgrid. But based on my experience and picture: The cell is stained from the text. It means only one thing. There is some space defined in front of the text. Probably an indentation of the text. Check it out.

There was a debate about something like this at TMS. The reason is a bug in Windows. I guess it applies to this case as well. I don't remember exactly.

It's a good thing we have lawyers. Otherwise I would understand everything

If you use themes, don't be surprised.

See GetIt

Team competition - how to do it Please advise. I'm sure there are some good ideas here. I have a rough idea, but it's severely lame. I'm asking for your suggestion on how to solve it and a suggestion for classes. That is, a methodology. I am not asking for the actual implementation. Problem to be solved: competition of cooperatives. Specifically football. It's in two stages. I want to solve each stage separately. The pictures tell more. 1) The first picture shows what the individual trees will look like in the elimination rounds. The elimination rounds, where everyone plays everyone The winners in the round will be dragged into the right tree 2) KO system All actions are always confirmed only for complete data and only once - the "Apply" button I will write everything in the DB.

I have found that for me, the best method to use in this case is the small incremental steps method. Per partes. That way the solution to the problem gradually emerges from the depths. Looks like I'm on the right track. Unfortunately, I can't explain it any better. I prefer classes for the record. I'm very fond of generics. I don't have to deal with performance. Thanks to all involved for trying to help me.

I don't understand part of the case. It doesn't say "condition". case condition of That is why I do not understand the whole proposal either.

1) Let's just look at the left part: group round It's a familiar scheme. Nevertheless, I find it very difficult to explain. ===== 2) I have the basic data written in the application. I have specified: teams in the first "Group round" number of Group round dynamically created graph for KO system That's all. ===== 3) In the meantime, I've decided that it will be good if all nodes in the Group round will have CheckBoxes. At the level of 0 (Group) they have no role 1 check mark means the advancing team ===== 4) The user's task is to move the advancing team to the adjacent right tree. If this is OK, the user will confirm this. Based on that, I will generate the teams in groups for that round. Here we handle this with the WriteToDB function ===== 6) It is up to the user whether to have it generated: matches (including rematches) list of players in each match These two points are not the task of this solution. Nor is entering data for the matches part of this task. ===== 7) I need to create the conditions to be able to: ReadFromDB: populate individual trees - I don't see a problem here hide unnecessary Group round in the code to accurately identify the individual rounds. So that I can set properties for them. For example: hidden, inaccessible, active. I don't need to identify the teams HERE. Then trees are enough for me. At least that's what I think. Write the result using WriteToDB 8) I'm not dwelling on the DB structure and working with it right now. That will follow smoothly from the problem itself. It's beyond the scope of this problem. ===== 9) The challenge is to design for point 7) correctly: data structures classes and their functions/methods Only the names of the functions, which will explain their operation - are sufficient.

I search, I search and I don't see it anywhere Put your minimum code here. So everyone here is just guessing.

The first form created is always the main one. We don't know how you create Form1.

Something like that. To make it easier for you to comment.