Sure but I wanted to know how he did it. I mean if he did using smo then obviously there is no Smo.EnumAvailbleOracleSevers() method so saying you can do it for SQL Server is pointless, if you used Smo.
Sorry - I was in the middle of organising unit testers this afternoon so I wasn't really paying too much attention to the subtleties. There are other ways of evaluating SQL Server instances, but I've never heard of one for Orrible.
Deja View - the feeling that you've seen this post before.
Post the exception message, stack trace and any other information it gives you. The more info you give the more likely someone will know the answer.
(Also, what do you mean by "my own system lock", do you mean an app that runs full screen and you have to type a password to close it? or do you mean a GINA replacement for the windows ctrl+alt+del -> lock computer screen?)
If i can provide you with more info please tell me what you need and ill get it for you,
This is the null reference exception which is basicly the same problem the call back crash is harder to reproduce while running inside VS.
As you can see its a full screen type password sort of thing, every keystroke will show another message from my guardian ninja until the correct password is typed in. (mouse gets hidden and clipped)
As you can see it doesnt actually crash inside my forms code but outside it in the program.cs
Type : System.AccessViolationException
Message : Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Source : System.Windows.Forms
StackTrace : at System.Windows.Forms.UnsafeNativeMethods.PeekMessage(MSG& msg, HandleRef hwnd, Int32 msgMin, Int32 msgMax, Int32 remove)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at Ninja.Program.Main() in C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Projects\Ninja\Ninja\Program.cs:line 27
TargetSite : Boolean PeekMessage(MSG ByRef, System.Runtime.InteropServices.HandleRef, Int32, Int32, Int32)
Weird, did you defiantly put the event subscribe line _before_ the application.run line?
What I'm after is the full exception details, in particular, the stack trace. If you can get them yourself, just post them, if not, can you stick your code online somewhere in a zip file & I'll have a look when I get home.
and the store procedure:
procedure PR_GET_CAMERA(I_PK_CAMERA_ID in CAMERA.PK_CAMERA_ID%type, O_CURSOR OUT CursorType, O_RETURN OUT NUMBER) AS
proc_name CONSTANT VARCHAR(255) := 'PR_GET_CAMERA';
o_return := 1;
OPEN O_CURSOR FOR
SELECT CAMERA.*, CAMERA_STATUS.DESCRIPTION as CAMERA_STATUS, ADDEVICE.ADD_DESCRIPTION as ADD_DESCRIPTION,
ADDEVICE.PK_ADD_ID as PK_ADD_ID, ADDEVICE.ADD_CAM_TYPE as IS_MOBILE_TYPE
ON ADDEVICE.PK_ADD_ID = CAMERA.FK_ADD_ID
ON CAMERA.FK_CAMERA_STATUS_ID = CAMERA_STATUS.PK_CAMERA_STATUS_ID WHERE PK_CAMERA_ID = I_PK_CAMERA_ID;
o_return := 0;
EXCEPTION WHEN OTHERS THEN
err_num := SQLCODE;
err_msg := 'SQLCODE: ' || SQLCODE || CHR(10) || err_msg || ':' ;
pr_store_error('Err', err_msg, err_num, proc_name);
I've checked and the id is passed properly to Load(), name of store proceduere is correct and the code works fine with different store procedures (id is different and name of procedure differs). SQL query similar to store procedure returns row without problem.
Hi. I want to create a dialog which shows the progress of a file copy operation. I'll be copying a batch of files, some of which are up to 40Mb, so I want to display the current file progress aswell as the total progress. The problem I'm having is when I invoke the method for updating the UI. Because I want to update each for file I'm having to cycle through the source file byte by byte and then invoke the method which is using up all my memory. This is what I have so far. Any help would be appreciated.
I see these totaly useless loops, why dont you just use File.ReadAllBytes and then write it out to file again and if you must have a byte by byte view. You can easily loop trough the byte array and write it out one by one.
And your why dont you just use the worker report progress function?
Well i hope this helps and maby i just dont get the picture.
Cheers for the reply. As I said, I need to display the current transfer progress for each file aswell as the total progress for all files so I need to write byte by byte (which it is doing) and then update the UI's progress bar with the current progress after each byte has been written. I'm not sure which loops you see as unnecessary btw as all 3 of them have a purpose. As for the workers' ProgressChanged event, it only has one value for percent complete and I need two.