Cross Unit DBF access

[Petrus Vorster]

Greeting all.

I have a form (unit1) with some TDBF controls on it.
It uses datagrids or tstringgrids to display some data.

I created another form in which some data is updated and saved back into one of those databases.

I have found that one cannot refer to TDBF control from another unit like you can do with normal controls. Inserting to a database which has controls connected to it on another form appears to be ignored.

Should I deactivate the Database on form 1 before form2 opens or is there a way to refer to that control on the first form?

Regards - Peter

[cdbc]

Hi
Take a look at my version 2 example in your other thread (post #8), the no-dbaware...
As you'll see, in that app, it would be _no_ problem to add another view and connect it to the 'Singleton' database-connection, but, alas, you keep toying with that ol' DBF-Shijt... 
(...and db-aware components)
Regards Benny

[Petrus Vorster]

Yes, that old DBF stuff might be old, but for my needs that is more than enough.
It is also simple to use.
I make desktop applications that helps where the workplace does not provide ad probably never will, and they will never allow me to make anything that will connect to a server or cloud databases.

I am way to close to retirement to bother with more complex stuff that I am never going to use.
I'm not in IT, and i'm a manager in a Medium size town with horrible infrastructure in a collapsing state. I am just holding everything together with zero funds and no interest from anywhere. 

You fellows here are WAY ahead of me. I honestly wish I joined here 15 years ago when I was still struggling with Freebasic/Powerbasic.

PS: I found the solution to my problem.
Do not activate the DBF connection on the unit two until the form is created.
Disable form1 connection, load form2, connect form2 DBF, Disconnect when close, Enable form1 DBF.

-thanks mate.
-Peter

[wp]

The recommended way to have multiple forms access the same database is to put the database component (TDbf) on a TDataModule; this is something like a hidden form for all non-visual components. You only must make sure that the datamodule is created before it is used (if you auto-create it it must be listed before the main form in "Project options" > "Forms". And of course, you must add the datamodule to the uses clauses of every form which accesses the database.

In the attachment I am showing you a small sample dbf in which the records are listed in the DBGrid in the mainform and the recors are edited in a dedicated editor form. Both forms are accessing the same dbf file on the datamodule.

[Petrus Vorster]

That is something that might work!

Thanks a million.

-Peter

[Petrus Vorster]

Thank you very much.

This was some great advice.
That does exactly what i need it to do.

-Peter