how to create a CString with huge lengh?

Printable View

Show 50 post(s) from this thread on one page

August 22nd, 2003, 06:04 AM
ovidiucucu

Quote:

Originally posted by Mick_2002
Wow...geez, I've never coded for the big boys :) Why don't you try your attitude when coding for medical devices?

I wrote some code for medical applications, but for sure I you don't know my atitude about coding.

I think we must leave this discussion. We can fight for something better.

Good luck and keep ahead, young man! ;)
August 22nd, 2003, 09:03 AM
Mick

Quote:

Originally posted by ovidiucucu
I wrote some code for medical applications, but for sure I you don't know my atitude about coding.

I think we must leave this discussion. We can fight for something better.

Good luck and keep ahead, young man! ;)

I was being sarcastic.

/GE Medical or GEMMS (ain't that a farking GEM)
August 22nd, 2003, 10:37 AM
wangnanjing

I have a huge SQLstring for selecting and inserting

Quote:

Originally posted by irona20
Well, I don't think that the SQL statment are so huge.
I had this problem once:

Code:

CString strAux = "SELECT DISTINCT \ GenInfInforme.sINFO_CODIGO, \ GenInfInformeDetalles.sIDET_VISTA, \ GenInfInformeDetalles.sIDET_CONSULTA, \ GenInfInformeDetalles.sIDET_USUARIO, \ GenInfArbolesCF.sGIAR_ARBOL, \ GenInfArbolesCF.nGIAR_COMPORT, \ GenInfArbolesCF.nGIAR_TIPOEJE, \ GenInfArbolesCF.nGIAR_PROFUN, \ GenInfArbolesCF.sGIAR_NODO, \ MasterTreesStructure.NodeCode, \ MasterTrees.TreeNumberOfLevels,\ MasterTreesStructure.NodeLevel, \ MasterTreesStructure.NodeTreeOrder \ FROM GenInfInforme INNER JOIN \ GenInfInformeDetalles ON \ (GenInfInformeDetalles.sINFO_CODIGO = GenInfInforme.sINFO_CODIGO) \ INNER JOIN Users ON (Users.UsuarioID = GenInfInforme.sINFO_USUARIO)\ INNER JOIN \ GenInfArbolesCF ON \ (GenInfInformeDetalles.sIDET_VISTA = GenInfArbolesCF.sGIAR_VISTA \ AND \ GenInfInformeDetalles.sIDET_CONSULTA = GenInfArbolesCF.sGIAR_CONSULTA \ AND \ GenInfInformeDetalles.sIDET_USUARIO = GenInfArbolesCF.sGIAR_USUARIO \ AND \ GenInfInformeDetalles.sINFO_CODIGO = GenInfArbolesCF.sGIAR_CODIGO) \ INNER JOIN \ MasterTrees ON \ (GenInfArbolesCF.sGIAR_ARBOL = MasterTrees.TreeMasterCode) \ INNER JOIN \ MasterTreesStructure ON \ (GenInfArbolesCF.sGIAR_ARBOL = MasterTreesStructure.TreeMasterCode) "; strAux += "WHERE ((GenInfInforme.bINFO_PRIVADO = 0 AND Users.GrupoID = '%s') OR \ GenInfInforme.sINFO_USUARIO = '%s') AND \ ((GenInfArbolesCF.nGIAR_TIPOEJE = 2) OR \ ((GenInfArbolesCF.nGIAR_TIPOEJE < 2) AND \ ((MasterTrees.TreeNumberOfLevels - 1) \ > MasterTreesStructure.NodeLevel))) AND \ ((GenInfArbolesCF.nGIAR_COMPORT = 0) OR \ ((GenInfArbolesCF.nGIAR_COMPORT > 0) AND \ ((MasterTrees.TreeNumberOfLevels - MasterTreesStructure.NodeLevel \ - 1) >= GenInfArbolesCF.nGIAR_PROFUN))) \ ORDER BY GenInfInforme.sINFO_CODIGO, \ GenInfInformeDetalles.sIDET_VISTA, \ GenInfInformeDetalles.sIDET_CONSULTA, \ GenInfInformeDetalles.sIDET_USUARIO, \ GenInfArbolesCF.sGIAR_ARBOL, \ MasterTreesStructure.NodeLevel, \ MasterTreesStructure.NodeTreeOrder";

I have to split my string because I get an error in runtime. So, maybe it is the same error.

Yes.I have the same situation as you. Because there are more than 100 fields in one single table of my DB, it makes the select and insert SQL very very long.
Actually,I tried this way:
CString sqlcmd1("SELECT [CONTINUOUS_FURNACE_NAME],[FURNACE_TYPE],[FURNACE_HEATING_TYPE],[IMAGE_PATH],[CONTINUOUS_FURNACE_TYPE],[OVERALL_W],[OVERALL_H],[WORK_SPACE_W], [WORK_SPACE_H],[ENTRY_OPENNING_AREA],[END_OPENNING_AREA],[MUFFLE],[BELT WIDTH],[BELT_MOVING],[BELT_UNIT_WEIGHT],[FURNACE_ EFFICIENY],[BELT_RETURN],[SHELL_COOLING_WATER_RATE],[THROU_AIR_FLOW],");
CString sqlcmd2("[ZONE_NUMBER],[Z1_LENGTH], [Z1_TRANSITION], [Z1_ATMOSPHERE], [Z1_FAN_HP],[Z1_ATMOSPHERE_FLOW],[Z1_CONNECTED_INPUT],[Z1_THROU_METAL_AREA],[Z2_LENGTH], [Z2_TRANSITION], [Z2_ATMOSPHERE], [Z2_FAN_HP],[Z2_ATMOSPHERE_FLOW],[Z2_CONNECTED_INPUT],[Z2_THROU_METAL_AREA],[Z3_LENGTH], [Z3_TRANSITION],[Z3_ATMOSPHERE], [Z3_FAN_HP],[Z3_ATMOSPHERE_FLOW],[Z3_CONNECTED_INPUT],[Z3_THROU_METAL_AREA],[Z4_LENGTH], [Z4_TRANSITION], [Z4_ATMOSPHERE], [Z4_FAN_HP],[Z4_ATMOSPHERE_FLOW],[Z4_CONNECTED_INPUT],[Z4_THROU_METAL_AREA],[Z5_LENGTH], [Z5_TRANSITION],[Z5_ATMOSPHERE], [Z5_FAN_HP],[Z5_ATMOSPHERE_FLOW],[Z5_CONNECTED_INPUT],[Z5_THROU_METAL_AREA],[Z6_LENGTH], [Z6_TRANSITION],[Z6_ATMOSPHERE], [Z6_FAN_HP],[Z6_ATMOSPHERE_FLOW],[Z6_CONNECTED_INPUT],[Z6_THROU_METAL_AREA],[Z7_LENGTH], [Z7_TRANSITION],[Z7_ATMOSPHERE], [Z7_FAN_HP],[Z7_ATMOSPHERE_FLOW],[Z7_CONNECTED_INPUT],[Z7_THROU_METAL_AREA],[Z8_LENGTH], [Z8_TRANSITION],[Z8_ATMOSPHERE], [Z8_FAN_HP],[Z8_ATMOSPHERE_FLOW],[Z8_CONNECTED_INPUT],[Z8_THROU_METAL_AREA],[Z9_LENGTH],[Z9_TRANSITION],[Z9_ATMOSPHERE],[Z9_FAN_HP],[Z9_ATMOSPHERE_FLOW],[Z9_CONNECTED_INPUT],[Z9_THROU_METAL_AREA],[Z10_LENGTH],[Z10_TRANSITION],[Z10_ATMOSPHERE],[Z10_FAN_HP],[Z10_ATMOSPHERE_FLOW],[Z10_CONNECTED_INPUT],[Z10_THROU_METAL_AREA],");
CString sqlcmd3("[HFACE_TOP1_THICK],[HFACE_TOP1_MAT],[HFACE_TOP2_THICK],[HFACE_TOP2_MAT],[HFACE_TOP3_THICK],[HFACE_TOP3_MAT],[HFACE_TOP4_THICK],[HFACE_TOP4_MAT],[HFACE_TOP5_THICK],[HFACE_TOP5_MAT],[HFACE_side1_MAT],[HFACE_side1_THICK],[HFACE_side2_MAT],[HFACE_side2_THICK],[HFACE_side3_MAT],[HFACE_side3_THICK],[HFACE_side4_MAT],[HFACE_side4_THICK],[HFACE_side5_MAT],[HFACE_side5_THICK],[HFACE_Bottom1_MAT],[HFACE_Bottom1_THICK],[HFACE_Bottom2_MAT],[HFACE_Bottom2_THICK],[HFACE_Bottom3_MAT],[HFACE_Bottom3_THICK],[HFACE_Bottom4_MAT],[HFACE_Bottom4_THICK],[HFACE_Bottom5_MAT],[HFACE_Bottom5_THICK] FROM [CONTINUOUS_FURNACE_DB]");

sqlcmd += sqlcmd1 ;
sqlcmd += sqlcmd2;
sqlcmd += sqlcmd3;
I printed out the sqlcmd at rumtime, it's a correct SQL.
But when it came to execute the sqlcmd, it throws a rumtime error like:[Microsoft][ODBC Microsoft access driver] Too few parameters.Expected 73. What's this?

Anyway,I am so grateful that so many nice people posting here.
Thanks!
wang
August 22nd, 2003, 10:46 AM
wangnanjing

here is my huge SQL string.Please help.

CString sqlcmd1("SELECT [CONTINUOUS_FURNACE_NAME],[FURNACE_TYPE],[FURNACE_
HEATING_TYPE],[IMAGE_PATH],[CONTINUOUS_FURNACE_TYP
E],[OVERALL_W],[OVERALL_H],[WORK_SPACE_W], [WORK_SPACE_H],[ENTRY_OPENNING_AREA],[END_OPENNING
_AREA],[MUFFLE],[BELT WIDTH],[BELT_MOVING],[BELT_UNIT_WEIGHT],[FURNACE_ EFFICIENY],[BELT_RETURN],[SHELL_COOLING_WATER_RATE
],[THROU_AIR_FLOW],");
CString sqlcmd2("[ZONE_NUMBER],[Z1_LENGTH], [Z1_TRANSITION], [Z1_ATMOSPHERE], [Z1_FAN_HP],[Z1_ATMOSPHERE_FLOW],[Z1_CONNECTED_INP
UT],[Z1_THROU_METAL_AREA],[Z2_LENGTH], [Z2_TRANSITION], [Z2_ATMOSPHERE], [Z2_FAN_HP],[Z2_ATMOSPHERE_FLOW],[Z2_CONNECTED_INP
UT],[Z2_THROU_METAL_AREA],[Z3_LENGTH], [Z3_TRANSITION],[Z3_ATMOSPHERE], [Z3_FAN_HP],[Z3_ATMOSPHERE_FLOW],[Z3_CONNECTED_INP
UT],[Z3_THROU_METAL_AREA],[Z4_LENGTH], [Z4_TRANSITION], [Z4_ATMOSPHERE], [Z4_FAN_HP],[Z4_ATMOSPHERE_FLOW],[Z4_CONNECTED_INP
UT],[Z4_THROU_METAL_AREA],[Z5_LENGTH], [Z5_TRANSITION],[Z5_ATMOSPHERE], [Z5_FAN_HP],[Z5_ATMOSPHERE_FLOW],[Z5_CONNECTED_INP
UT],[Z5_THROU_METAL_AREA],[Z6_LENGTH], [Z6_TRANSITION],[Z6_ATMOSPHERE], [Z6_FAN_HP],[Z6_ATMOSPHERE_FLOW],[Z6_CONNECTED_INP
UT],[Z6_THROU_METAL_AREA],[Z7_LENGTH], [Z7_TRANSITION],[Z7_ATMOSPHERE], [Z7_FAN_HP],[Z7_ATMOSPHERE_FLOW],[Z7_CONNECTED_INP
UT],[Z7_THROU_METAL_AREA],[Z8_LENGTH], [Z8_TRANSITION],[Z8_ATMOSPHERE], [Z8_FAN_HP],[Z8_ATMOSPHERE_FLOW],[Z8_CONNECTED_INP
UT],[Z8_THROU_METAL_AREA],[Z9_LENGTH],[Z9_TRANSITI
ON],[Z9_ATMOSPHERE],[Z9_FAN_HP],[Z9_ATMOSPHERE_FLO
W],[Z9_CONNECTED_INPUT],[Z9_THROU_METAL_AREA],[Z10
_LENGTH],[Z10_TRANSITION],[Z10_ATMOSPHERE],[Z10_FA
N_HP],[Z10_ATMOSPHERE_FLOW],[Z10_CONNECTED_INPUT],
[Z10_THROU_METAL_AREA],");
CString sqlcmd3(" [HFACE_TOP1_THICK],[HFACE_TOP1_MAT],[HFACE_TOP2_TH
ICK],[HFACE_TOP2_MAT],[HFACE_TOP3_THICK],[HFACE_TO
P3_MAT],[HFACE_TOP4_THICK],[HFACE_TOP4_MAT],[HFACE
_TOP5_THICK],[HFACE_TOP5_MAT],[HFACE_side1_MAT],[H
FACE_side1_THICK],[HFACE_side2_MAT],[HFACE_side2_T
HICK],[HFACE_side3_MAT],[HFACE_side3_THICK],[HFACE
_side4_MAT],[HFACE_side4_THICK],[HFACE_side5_MAT],
[HFACE_side5_THICK],[HFACE_Bottom1_MAT],[HFACE_Bot
tom1_THICK],[HFACE_Bottom2_MAT],[HFACE_Bottom2_THI
CK],[HFACE_Bottom3_MAT],[HFACE_Bottom3_THICK],[HFA
CE_Bottom4_MAT],[HFACE_Bottom4_THICK],[HFACE_Botto
m5_MAT],[HFACE_Bottom5_THICK] FROM [CONTINUOUS_FURNACE_DB]");

sqlcmd += sqlcmd1 ;
sqlcmd += sqlcmd2;
sqlcmd += sqlcmd3;

I MessageBox the sqlcmd at rumtime, it's correct.
But when it came to execute the sqlcmd, it throws a rumtime error like:[Microsoft][ODBC Microsoft access driver] Too few parameters.Expected 73.
What's this?

Anyway,I am so grateful that so many nice people here.
Thanks!;)
August 22nd, 2003, 11:00 AM
Sam Hobbs

You might get better help in a database forum.

You can debug SQL using Access or SQL Server.
August 22nd, 2003, 11:06 AM
Paul McKenzie

Why didn't you post this in the thread you started earlier?

First, I would make the command easier to handle:

Code:

CString sqlcmd; sqlcmd = "SELECT [CONTINUOUS_FURNACE_NAME]," "[FURNACE_TYPE]," "[FURNACE_HEATING_TYPE]," "[IMAGE_PATH]," "[CONTINUOUS_FURNACE_TYPE]," "[OVERALL_W]," "[OVERALL_H]," "[WORK_SPACE_W]," "[WORK_SPACE_H]," "[ENTRY_OPENNING_AREA]," "[END_OPENNING_AREA]," "[MUFFLE]," "[BELT WIDTH]," "[BELT_MOVING]," // etc.

Note what I did. I seperated each column into a seperate line. In C and C++, you can have express a long string by breaking up the string into individual strings. This makes your code easier on the eyes, and easier to see if there is any problem with your SQL statement. It also makes this not necessary:

Code:

sqlcmd += sqlcmd1 ; sqlcmd += sqlcmd2; sqlcmd += sqlcmd3;

I don't know why you did this when CString can work correctly.

Also, in your other post, you mentioned you used MessageBox to "print the query". This is not a good idea. Again, you are relying by sight to see if the SQL query is valid. It is just too large a query to really know if it will work without actually testing it. Did you test the query, not just print it out? Instead, do the following:

Code:

sqlcmd = YourLongCommand; OutputDebugString( (LPCTSTR) sqlcmd );

If you run in the debugger, the entire command will show up in the Output Window of VC++. Now copy and paste the string you see in the output window and place it into some program that accepts SQL queries (Access, SQL Server, whatever). Did the query work? If it doesn't, then you see what is wrong with the query you built, not what is wrong with CString. If it does work, then the problem is not with CString, but some other database/OBDC related issue.

Regards,

Paul McKenzie
August 22nd, 2003, 04:46 PM
Andreas Masur

[Merged threads]

wangnanjing, please keep the same question within the same thread. Thank you very much.
August 23rd, 2003, 03:15 AM
panayotisk

Thanx for the tips guys,
Is their a difference between using OutputDebugString() and the TRACE macro?
Also is there a way to see unicode characters in the Output Window, since some queries may contain Unicode strings?
August 23rd, 2003, 11:41 AM
Sam Hobbs

Quote:

Originally posted by panayotisk
Is their a difference between using OutputDebugString() and the TRACE macro?

If it were me, I would look at the documentation of OutputDebugString() and the TRACE macro and if I was unsure of what the TRACE macro does I would look at the TRACE macro source to see what it does. Then if there was something in particular I did not understand I would ask something about that.

I sure don't understand what "difference" you are asking. Perhaps you are asking which is easier to use. The TRACE macro includes a formatting capability that you don't get if you use OutputDebugString directly, but that difference is obvious when the documentation is read.
August 25th, 2003, 06:00 AM
panayotisk

Quote:

...but that difference is obvious when the documentation is read.

Yes, that difference is quite obvious.

Show 50 post(s) from this thread on one page