mohamadardaneh
Programmer
hello
foxpro 9 siad :
"alias:goapp was not found"
please guide me
thank you so much
foxpro 9 siad :
"alias:goapp was not found"
please guide me
thank you so much
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
foxpro9
- Thread starter mohamadardaneh
- Start date
- Status
Mike Lewis
Programmer
This was caused by an error in your code. You are referencing "goapp" as an alias of a table. But that alias was not found. Hence the error.
"goap" is more likely to be an object rather than an alias, although I can't be sure about that without seeing your code.
If you would post the section of code where the error occurred, we might be able to help.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
"goap" is more likely to be an object rather than an alias, although I can't be sure about that without seeing your code.
If you would post the section of code where the error occurred, we might be able to help.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
Visual FoxPro articles, tips and downloads
Olaf Doschke
Programmer
As Mike already said goApp by convention is a global object (=go) of an Application (=app), or "the" application object. But it's not something you have natively in VFP, it's not a missing VFP component or such.
It's a convention of many if not all application frameworks (libraries on top of the core language used to create applications faster than starting from scratch) to have such an object you can rely on existing and that provides several centrally necessary functionalities or even just properties, like the application name stored in a goApp property like goApp.ApplicationName.
Usually, that goApp object is not just created as start code of an EXE but also created in the IDE during development, as it may even provide such central features for "wizards" and "builders" (two further topic I won't deep dive into here).
Some frameworks configure VFP to always run code at startup by setting _Startup, some add a project hook into projects that initializes that whenever you open up the project, some rely on the developer to start a framework booting PRG.
At this point, it should become clear: Follow instructions. If you don't have any, you need to deep dive into code analysis, but the main prg of a project should be what you look into first.
Project modules based on a framework, also SCX forms, reports, PRGs, that you usually can start without any bootup obviously will fail on the first line addressing goApp, when that isn't created.
So you first have to start the major framework "boot code" to create goApp before you do anything else in such projects.
Bye, Olaf.
Olaf Doschke Software Engineering
It's a convention of many if not all application frameworks (libraries on top of the core language used to create applications faster than starting from scratch) to have such an object you can rely on existing and that provides several centrally necessary functionalities or even just properties, like the application name stored in a goApp property like goApp.ApplicationName.
Usually, that goApp object is not just created as start code of an EXE but also created in the IDE during development, as it may even provide such central features for "wizards" and "builders" (two further topic I won't deep dive into here).
Some frameworks configure VFP to always run code at startup by setting _Startup, some add a project hook into projects that initializes that whenever you open up the project, some rely on the developer to start a framework booting PRG.
At this point, it should become clear: Follow instructions. If you don't have any, you need to deep dive into code analysis, but the main prg of a project should be what you look into first.
Project modules based on a framework, also SCX forms, reports, PRGs, that you usually can start without any bootup obviously will fail on the first line addressing goApp, when that isn't created.
So you first have to start the major framework "boot code" to create goApp before you do anything else in such projects.
Bye, Olaf.
Olaf Doschke Software Engineering
- Status