Hi,
I have to change the database name (provider restrictions ) in my project.
Starting a new project gives no opportunity to use already define tables from the older project.
Or.... what do I miss?
I thought: Copy all the files to a new directory = database name, change the config.php and Yep that does the trick ..... nothing of that.
Ron
New project - using old tables
Re: New project - using old tables
FOUND IT
Scrolling to some documentation a came to:
Import your existing MySQL/MariaDB database schema to AppGini --> https://bigprof.com/appgini/m2a
Followed the mentioned steps and .... YEP I'm a Happy Camper.
AppGini, your documentation is perfect, thank you
Ron
Scrolling to some documentation a came to:
Import your existing MySQL/MariaDB database schema to AppGini --> https://bigprof.com/appgini/m2a
Followed the mentioned steps and .... YEP I'm a Happy Camper.
AppGini, your documentation is perfect, thank you
Ron
Re: New project - using old tables
At second thougts .....
It seems that after using m2a.php procedure the generated .AXP file has indeed the wanted tables imported however, all the field definitions has to be set again.
So, coming back to my first post: How can I "import" old defined tables to a new project ?
Ron
It seems that after using m2a.php procedure the generated .AXP file has indeed the wanted tables imported however, all the field definitions has to be set again.
So, coming back to my first post: How can I "import" old defined tables to a new project ?
Ron
Re: New project - using old tables
Well,
It is so simple and so stupid of me.
Change database-name in config.php
Change Database-name in the .AXP application.
I think I was somewhere else in mind the other day.
Ron
It is so simple and so stupid of me.
Change database-name in config.php
Change Database-name in the .AXP application.
I think I was somewhere else in mind the other day.
Ron
Re: New project - using old tables
We all have those days