Call to modules in front / back ends

greaseman

Closer to seniority!
Local time
Today, 11:56
Joined
Jan 6, 2003
Messages
360
I have an application that is broken out to a front end / backend. In the FE, are some modules that call to modules in the app's BE. That part works great. However, there are some places in the BE that I want to have call to a module or two in the FE, and that part doesn't work at all. I get errors that tell me the FE module can't be found.

All I want is for the FE to call to modules in the BE, and the BE, when its active to be able to call to modules in the FE.

Any ideas, comments and suggestions are appreciated. Thank you.
 
This won't really help you, but I must ask why you would have modules in the back end? I've always split my database so that all object and code were in the front end, only tables were in the back end.
 
Why modules in both places?

We have modules in both places because actually the back end we are using is a collection of routines that is a "black box" -type library. It is where all of our universal routines, codes, etc. reside. What we have is:

Front End Two-Part Back-end, 1/2 of which is only data, the other portion being our universal modules.

Its like a fork in the road. So....we've succeeded in making calls from the FE to our library part of our BE, but don't seem to be able to have the BE library make calls to the FE modules.

Any and all help is appreciated.
 
Why don't you you just but the modules in the BE. And make your life 10x easier? Frontends may be always moving around to different users, the backend aint going anywhere.
________
Vaporizer Shop
 
Last edited:

Users who are viewing this thread

Back
Top Bottom