We have an issue in the office where on several of our PC's when
launching our software 4D Client 2003.8 will quit when it hits the
Active4D plug-in command "A4D Init". I have a Win2000 box running
4D Client and it behaves normally, but in our office at least four
Windows machines running 4D Client will quit out of Client when
this command is hit. On the Mac side things work wonderfully.
WinXP or Win2000
4D Client 2003.8
Active4D v4.0 (current shipping version)
Mac OSX 10.4.x (works great)
If we load the last beta of Active4D in the Win4DX folder
everything works fine. It is only with the current shipping 4.0
version that things go south for us. Anyone have ideas as to what
to look at?
If the previous version works, it could be you did not correctly
update the structure with the latest shell code.
Do you really want _every_ Client to act as a web server? If not, you
should only be turning <>A4D_ClientIsWebServer on for those Clients
that need to be running Active4D.
Also, it has been reported that a file name greater than 80
characters in length placed in the "web"
folder will crash 4D when A4D Init is called.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
