Why would you want to create an .exe ? There's possibilities to create an .exe from any Magic application but why would you do this ? In Java or .NET you do not either. If its a RIA application and yo

#please #chat #temp #ria

so , you say that ,there is no any option to create .exe file with magic.Right!

#please #chat #temp #ria

Like all Magic deployments, RIA does not involve creating an .EXE file.

#please #chat #temp #ria

Vikash Should I create .exe file of my project in magic XPA 3.1. If is it possible then guide us. Many thanks.

#please #chat #temp #ria

Hi Steven, The Magic Activity monitor is the wrong place to check for this, look in the MSSQL monitor Check existence is indeed the only way to create these temp. tables because creating them with dir

#temp

In MSSQL there are two types of temp tables global or local, designated by #table_name or ##table_name Many times Magic will create multiple connections to SQL - particularly a direct sql connection e

#temp

Hi Steven. I, too, have had this issue in the past and no amount of debugging or log analysis could find a consistent reason for it. Andreas' explanation sounds the most likely, however. I gave up usi

#temp

The tables have Check Existence YES, because I has to or Magic wont make one at all. So if it is a new connection, then Magic should request a new one. We are pretty sure that it isn’t a new connectio

#temp

P.S.: You might want to play with the max connections (in dbms or database properties). If you limit your max connections to one (default is 0 resp. 10 then I think) and Magic does not simply ignore t

#temp

Hi Steven, I do not really work much with Magic & MSSQL since longer so I did not run in that problem since longer and things change as well. The issue might be that it is not always clear if and when

#temp

We thought this was OK, but suddenly we are getting issues with the use of MSSQL #Temp tables. We are now getting lots of “Cannot find the object “#Temp” because it does not exist or you do not have p

#temp

Yes, I know, _everyone_ seems to be reporting problems with #temp tables at the moment, but this is another variation. This is what happens: SQL Server 2000, Magic 8.3 SP9 1) A batch process successfu

#temp