OK, I give up, what error did you get? Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman

You might have slightly more luck by asking this question in the proper forum. "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous

#include <time.h> clock_t start=clock(); //... clock_t end=clock(); unsigned int dis_time=end-start;

You should avoid this coding style as it may lead to some serious problems. Google SQL Injection, you yourself will understand.

What do you want arr2 to look like when done? +-----+-----+-----+-----+-----+ | 100 | 200 | 300 | 400 | 500 | +-----+-----+-----+-----+-----+ | | | | | | +-----+-----+-----+-----+-----+ or +-----+-----+-----+-----+-----+ | | | | | | +-----+-----+-----+-----+-----+ | 100 | 200 | 300 | 400 | 500 | +-----+-----+-----+-----+-----+ "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "Some people are making such thorough preparation for rainy days that they aren't enjoying today's sunshine." - William Feather

tagopi, This is the solution that was posted by WayneAKing in the Visual C++ Developer Center forum. His posting is in response to an error listing that I posted. This guy knows everything. My program is now working. I added the directory to the project configuration >properties - linker - general tab. That's half the requirements. What did I say to add, and where did I say to add it? Look under Linker->Input for "Additional Dependencies" and add your .lib filename to the list. >int main() You are making a console program. >error LNK2019: unresolved external symbol _WinMain@16 >referenced in function ___tmainCRTStartup WinMain is used with Win32 GUI applications, not console apps. How did you create the project? Which project template did you use? You should have selected "Win32 Console Application". Look under Linker->System for "SubSystem" and set it to "Console (/SUBSYSTEM:CONSOLE)" - Wayne

Hi, Could be some kind of syntax issue in the SQL statement itself. Also if I rememeber correctly the parameter usage in the sql statement may be provider specific so if the SQL statement is otherwise fine could it be because of the question mark. You could try literals as a test n order to see if that's the case. Also perhaps the following link would help you: http://msdn.microsoft.com/en-us/library/ms677554(v=VS.85).aspx[^] The need to optimize rises from a bad design.My articles[^]

You cannot directly use local variables inside your SQL statements. You can use a Parameter object to pass a value from a variable to the statement. For example see, http://msdn.microsoft.com/en-us/library/ms677589(VS.85).aspx[^] The need to optimize rises from a bad design.My articles[^]

Your while loop initializes the array roll with values between 1 and 10. Note that there is no guarantee every value between 1 and 10 will actually be stored in roll somewhere; for all you know it might be an array full of 1s or full of 10s! In your first for loop you increment loop num times, then access roll[loop+1]; on the last loop you will read past the end of the array, invalidating the comparison, so if the biggest value in your array happens to be stored in the last element, it may or may not be stored in temp. In Debug this probably won't cause a problem, as likely roll[100] would just access fin[0] instead, and that would be initialized to 0. In Release mode however there is no guarantee that the array fin will be initialized to 0 - in my experience it most likely will not. The intention of the first for loop appears to be to find the largest value in roll and store it in temp. Note that this value may be anything between 1 and 10! The error you noticed, however, is due to what the others already pointed out above: you shouldn't increment cyc in the outer loop! What happens is this: the inner loop finds all items in roll that correspond to the temp value, store it in fin, and increment (correctly) the index cyc. Once you're at the end of the loop, temp gets decremented, then cyc gets incremented again, causing the gap you noticed, then you go on searching for occurences of your now decreased value of temp. The reason for this confusion is that the outer loop is really all about temp, not cyc! The clearest way to write your last loop would be like this: cyc = 0; for (int compare = temp; compare > 0; compare--) { for (loop = 0; loop < LIMIT; loop++) { if (roll[loop] == compare) { fin[cyc] = compare; cyc++; } } } Note that I replaced num with LIMIT. This doesn't change anything in your code, but it is easier to read, as a reader unfamiliar with your code doesn't have to interpret all of it just to find out what value num would hold. Also it's less likely to accidentally mess up if you later change your code and possibly change the value of num. Now, while the above is clearer, it is also potentially less efficient; you used the c

Why not: strncpy(Date[cyc], (char *)orig, TARGSIZE - 1); // or even (what type is orig?) strncpy(Date[cyc], (char *)rec->Fields->GetItem("Time")->Value, TARGSIZE - 1); I must get a clever new signature for 2011.

Disregarding the method of conversion, the assignment you used attempts to assigns an array of characters to single character: Date is defined as an array of ARR characters, and Date[cyc] denotes the character with the index cyc within that array. What was your intention? I suspect that what you really wanted is to define Date as an array of strings rather than as an array of characters. In this case you should define Date as char* Date[ARR];. On a sidenote, what you are trying to achieve is like pouring milk into a crate for beer bottles: you can't just go ahead and assign the contents of one variable to another variable that is designed to hold something completely different - doing this will usually result in spilling the contents. Instead you have to use the proper function or method for transfering the contents of one variable into the other. Plus you might need to allocate proper containers first: so first thing, pick up an empty beer bottle, then pour the milk into it, and only then you can put that bottle into the crate. With respect to these strings, the Date array corresponds to the crate for beer bottles. The beer bottles correspond to char-strings, and the milk corresponds to the contents of that _bstr_t. So what you have to do is: - allocate an array of char, big enough to hold the _bstr_t - call the appropriate method to convert a _bstr_t into a char*, and then - put it into the Date array.

And you don't have to look there, what matters is the documentation: isalpha return a boolean result, either zero or non-zero; since the different non-zero values are not documented, you should not rely on them. Nor on any observation you may make, not in a .h file and not when running a test app. :) Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.

1 more thing I missed at a first glance. For the case when the user presses q to quit, they still need to enter a float for the weight. you should have the 2nd scanf inside an if to check for that

Nuri, Oh, my.... I feel so dumb. Thank you for your help.

A loop such as for(row=0;row<=1;row++) should be read like this: 'Set row to 0, and then keep adding 1 to row until row is no longer less or equal to 1.' So what happens is this: First iteration (row is now 0): Is row <= 1? Yes; execute the code in the loop's body and when that's done, add 1 to row. Second iteration (row is now 1): Is row <= 1? Yes; execute the code in the loop's body and when that's done, add 1 to row. Third iteration (row is now 2): Is row <= 1? No; execute the code after the loop. So although row is equal to 2 áfter the loop, row is always less or equal to 1 within the loop.

As Cedric already said, you really should get a good book, there's just too many problems with your code way beyond the syntactical issues your compiler complains about. The latter is due to your apparent misunderstanding on the scope of variables in C/C++. If you declare a variable, this variable is only known within the scope it is declared in. In most cases this scope is between the previous opening '{' and the corresponding closing '}'. There are basically two exceptions: If you define a variable within the definition of a class (or a struct), then every function that is also defined as a member of that class has access to it. The other exception is when you declare a variable outside a function or class (or struct), which makes it a global variable. Global variables may be accessed anywhere, provided it's declaration comes prior to the location where it's defined. Check your C/C++ book of choice for further explanations on how to declare and access global variables. However, it is a good practice to keep the number of global variables to a minimum. The compiler states that PropNameArray is an undeclared identifier because within the scope of the main function, the variable PropNameArray is not known. It is only known within the function PropInit(), where this variable was declared. Note that all variables will be automatically destroyed when program execution leaves the scope they are declared in. In other words, when you execute the function PropNameInit(), the system will first create all these variables, then initialize them, and, when it leaves the function, immediately destroy them again. As has been pointed out in another response, the function PropInit() currently does nothing! You have three options: 1. Make the variables global (which is bad design). 2. Create the variables outside of the function (i. e. in main) and pass them as arguments to the function PropInit (which is impractical) 3. Declare these variables as attributes of the class Hope this helps to get you started, but like stated before, do yourself a favor and get a book.

My bad. I was using a slightly aged version of MSDN. "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "Man who follows car will be exhausted." - Confucius