BorlandTalk.com Borland discussion newsgroups   Archives   FAQ   Search   Memberlist   Usergroups   Register   Profile   Log in to check your private messages   Log in  Error Message after build don't send me to right line of cod Goto page 1, 2, 3, 4  Next          BorlandTalk.com Forum Index -> C++ Builder (IDE) View previous topic :: View next topic   Author Message server Guest Posted: Sun Feb 05, 2006 12:27 am    Post subject: Error Message after build don't send me to right line of cod message unavailable Back to top Roddy Pratt Guest Posted: Sun Feb 05, 2006 12:27 am    Post subject: Re: Error Message after build don't send me to right line of Please have a look at/vote/rate QC 23782, and add a comment to it if you have a reproducable case, or open a fresh QC if you think it's a different problem. - Roddy Back to top Lars Christensen Guest Posted: Tue Feb 07, 2006 9:00 pm    Post subject: Re: BDS2006 oftsream gives CodeGuard error Lars Christensen wrote: Quote: In a otherwise empty VCL-project, the following code snip allways generates an code guard error: I have found a work around. If I turn "Use Dynamic RTL" off, then the problem is gone. -- Best regards, Lars A. Christensen Back to top Paul Guest Posted: Tue Feb 07, 2006 11:00 pm    Post subject: Re: How to use DLLs As per attachments group reply: I have tried the articles and have had some success today with the explicit DLL access (example 2). I tried the implicit (example 1), but I couldn't get it to work with VC++ 2005 Express Edition. Someone at work suggested that the DEF mechanism wasn't really supported by MS anymore, not sure if this is true or not. I'm going to persist with the example 2 mechanism to get the initial job done, but may go back to example 1 at a later stage. Thanks Paul. <Mark Jacobs> wrote in message news:43de8ec1$1 (AT) newsgroups (DOT) borland.com... Back to top HF Guest Posted: Wed Feb 08, 2006 10:00 am    Post subject: Re: BDS2006 oftsream gives CodeGuard error In BCB 5 is working without any errors. ? "Lars Christensen" <lac (AT) geoteknisk (DOT) dk> ?????? ??? ?????? news:43e905c1$1 (AT) newsgroups (DOT) borland.com... Quote: Lars Christensen wrote: In a otherwise empty VCL-project, the following code snip allways generates an code guard error: I have found a work around. If I turn "Use Dynamic RTL" off, then the problem is gone. -- Best regards, Lars A. Christensen Back to top Lars Christensen Guest Posted: Wed Feb 08, 2006 1:01 pm    Post subject: Re: BDS2006 oftsream gives CodeGuard error HF wrote: Quote: In BCB 5 is working without any errors. It should. It's legal C++ code. -- Best Regards Lars Back to top David Ayre Guest Posted: Sat Feb 11, 2006 10:03 am    Post subject: Re: compiling projects from BCB6 & BCB4 with 2006 "David Ayre" <davidcayre (AT) ntlworld (DOT) com> wrote: Quote: Raul Lorenzo <rlorenb (AT) agalisa (DOT) es> wrote: I recommend what Remy told you, I had problems too when updating my projects from BCB6 to BDS2006, not related with memory manager, related to EResNotFound instead, so, i created the project files from scratch and all worked. I know it is a shit but its better. Mucho gracias Raul, I'll have a go at that. It does seem a bit tedious, but once it's done everything should run smoothly. I hope. Hasta la vista, David I tried that on the most problematic and it seemed to work OK. Thanks for your help, David Back to top Roddy Pratt Guest Posted: Wed Jun 14, 2006 3:25 pm    Post subject: Re: Weard CodeGuard message "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448fdc92 (AT) newsgroups (DOT) borland.com... Quote: CodeGuard got me this weard message. "Attempt to access 4 byte(s) at 0x003C674D+10, that is at offsett 0+10 in block 0x003C674D(=SomeMyDll.DLL:0x02:00674D) which is only 11 bytes long." What can it means "only 11 bytes" if the access is to 4 bytes? "weird" is the spelling you need. It's trying to read 4 bytes at offset 0x10 in a block that is only 11 bytes long. So it IS trying to access outside the block. - Roddy Back to top mauro russo Guest Posted: Wed Jun 14, 2006 4:14 pm    Post subject: Re: Weard CodeGuard message suspected Code Guard or Linker error!!! In the attached file [on borland.public.attachments] it is showed the screenshot of my pc. Yuo can note that all parameters of the CALL_GDA_EGY that catches the problem are constants (except eax) [eax (0x00 in my case) 0x00, 0x04, 0x003c674d, 0x0a]. So, it means it should be: a) an error of the linker b) an error of "inserting" code of CodeGuard facilities. c) what else? In fact the problem seems to be 0x0a [the message CodeGuard reads 'at 0x003C647D+10...']. You can also note that the problem is catched for the third call to CALL_GDA_EGY. Does it mean that the problem is for the third parameter? [MAX_LENGT_MESSAGES that is a #define (value 127)] or the third-last parameter? [the constant 0]. I hope you can confirm what parameter is it, so i'll concentrate to investigate on only that parameter. In the second attachment i report the following asm-code of the method-call-code and the CodeGuard Window. PS: i'll post the two files on the .attachment newsgroup in some minutes. Thank you to pay attention, Mauro. "Roddy Pratt" <roddy at spam fritter dot com> ha scritto nel messaggio news:448fe42a (AT) newsgroups (DOT) borland.com... Quote: "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448fdc92 (AT) newsgroups (DOT) borland.com... CodeGuard got me this weard message. "Attempt to access 4 byte(s) at 0x003C674D+10, that is at offsett 0+10 in block 0x003C674D(=SomeMyDll.DLL:0x02:00674D) which is only 11 bytes long." What can it means "only 11 bytes" if the access is to 4 bytes? "weird" is the spelling you need. It's trying to read 4 bytes at offset 0x10 in a block that is only 11 bytes long. So it IS trying to access outside the block. - Roddy Back to top mauro russo Guest Posted: Wed Jun 14, 2006 5:14 pm    Post subject: Re: Weard CodeGuard message That's the state of my investigation: The parameters are (as documented and as i'm sure you know already) pushed on the stack in the opposite order. The problem is catched for the parameters mess (the empty "" in my case). In fact the address passed is 0x3C6757 that is just 0x3C674D+0x0a. I'll check how CALL_GDA_EGY extracts the 'length 11'. The main point is that i really suspect a CodeGuard or a Linker error, because now i'm almost sure that is about the parameter "". That's constant allocated in the space beginning in 0x3C673C (as reported in the line of the .map file that i post already). How hope some of you can support what i believe, analyzing the attachments in news:448ff14a (AT) newsgroups (DOT) borland.com... Thank you, Mauro. "mauro russo" <m.russo (AT) uniplan (DOT) it> ha scritto nel messaggio news:448fefb5 (AT) newsgroups (DOT) borland.com... Quote: suspected Code Guard or Linker error!!! In the attached file [on borland.public.attachments] it is showed the screenshot of my pc. Yuo can note that all parameters of the CALL_GDA_EGY that catches the problem are constants (except eax) [eax (0x00 in my case) 0x00, 0x04, 0x003c674d, 0x0a]. So, it means it should be: a) an error of the linker b) an error of "inserting" code of CodeGuard facilities. c) what else? In fact the problem seems to be 0x0a [the message CodeGuard reads 'at 0x003C647D+10...']. You can also note that the problem is catched for the third call to CALL_GDA_EGY. Does it mean that the problem is for the third parameter? [MAX_LENGT_MESSAGES that is a #define (value 127)] or the third-last parameter? [the constant 0]. I hope you can confirm what parameter is it, so i'll concentrate to investigate on only that parameter. In the second attachment i report the following asm-code of the method-call-code and the CodeGuard Window. PS: i'll post the two files on the .attachment newsgroup in some minutes. Thank you to pay attention, Mauro. "Roddy Pratt" <roddy at spam fritter dot com> ha scritto nel messaggio news:448fe42a (AT) newsgroups (DOT) borland.com... "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448fdc92 (AT) newsgroups (DOT) borland.com... CodeGuard got me this weard message. "Attempt to access 4 byte(s) at 0x003C674D+10, that is at offsett 0+10 in block 0x003C674D(=SomeMyDll.DLL:0x02:00674D) which is only 11 bytes long." What can it means "only 11 bytes" if the access is to 4 bytes? "weird" is the spelling you need. It's trying to read 4 bytes at offset 0x10 in a block that is only 11 bytes long. So it IS trying to access outside the block. - Roddy Back to top Pete Fraser Guest Posted: Wed Jun 14, 2006 5:41 pm    Post subject: Re: Weard CodeGuard message What's the line of code where CodeGuard is showing the problem? CodeGuard doesn't normally get it wrong - I normally find that I made a mistake. Pete "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448ffd9b (AT) newsgroups (DOT) borland.com... Quote: That's the state of my investigation: The parameters are (as documented and as i'm sure you know already) pushed on the stack in the opposite order. The problem is catched for the parameters mess (the empty "" in my case). In fact the address passed is 0x3C6757 that is just 0x3C674D+0x0a. I'll check how CALL_GDA_EGY extracts the 'length 11'. The main point is that i really suspect a CodeGuard or a Linker error, because now i'm almost sure that is about the parameter "". That's constant allocated in the space beginning in 0x3C673C (as reported in the line of the .map file that i post already). How hope some of you can support what i believe, analyzing the attachments in news:448ff14a (AT) newsgroups (DOT) borland.com... Thank you, Mauro. "mauro russo" <m.russo (AT) uniplan (DOT) it> ha scritto nel messaggio news:448fefb5 (AT) newsgroups (DOT) borland.com... suspected Code Guard or Linker error!!! In the attached file [on borland.public.attachments] it is showed the screenshot of my pc. Yuo can note that all parameters of the CALL_GDA_EGY that catches the problem are constants (except eax) [eax (0x00 in my case) 0x00, 0x04, 0x003c674d, 0x0a]. So, it means it should be: a) an error of the linker b) an error of "inserting" code of CodeGuard facilities. c) what else? In fact the problem seems to be 0x0a [the message CodeGuard reads 'at 0x003C647D+10...']. You can also note that the problem is catched for the third call to CALL_GDA_EGY. Does it mean that the problem is for the third parameter? [MAX_LENGT_MESSAGES that is a #define (value 127)] or the third-last parameter? [the constant 0]. I hope you can confirm what parameter is it, so i'll concentrate to investigate on only that parameter. In the second attachment i report the following asm-code of the method-call-code and the CodeGuard Window. PS: i'll post the two files on the .attachment newsgroup in some minutes. Thank you to pay attention, Mauro. "Roddy Pratt" <roddy at spam fritter dot com> ha scritto nel messaggio news:448fe42a (AT) newsgroups (DOT) borland.com... "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448fdc92 (AT) newsgroups (DOT) borland.com... CodeGuard got me this weard message. "Attempt to access 4 byte(s) at 0x003C674D+10, that is at offsett 0+10 in block 0x003C674D(=SomeMyDll.DLL:0x02:00674D) which is only 11 bytes long." What can it means "only 11 bytes" if the access is to 4 bytes? "weird" is the spelling you need. It's trying to read 4 bytes at offset 0x10 in a block that is only 11 bytes long. So it IS trying to access outside the block. - Roddy Back to top mauro russo Guest Posted: Wed Jun 14, 2006 9:34 pm    Post subject: Re: Weard CodeGuard message "Pete Fraser" <pete.nospam.fraser.nospam (AT) frasersoft (DOT) nospam.net> wrote in the message news:449003eb$1 (AT) newsgroups (DOT) borland.com... Quote: What's the line of code where CodeGuard is showing the problem? In the call of method CodeAck. Quote: CodeGuard doesn't normally get it wrong - I normally find that I made a mistake. I never told that it gets wrong the number of the line. I told that it gets wrong the error, or that the linker made a mistake. The motivation of my thinking is that Codeguard shows the problem in accessing a constant parameter, that's the const char array "". Quote: Pete Mauro Russo. Quote: "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448ffd9b (AT) newsgroups (DOT) borland.com... That's the state of my investigation: The parameters are (as documented and as i'm sure you know already) pushed on the stack in the opposite order. The problem is catched for the parameters mess (the empty "" in my case). In fact the address passed is 0x3C6757 that is just 0x3C674D+0x0a. I'll check how CALL_GDA_EGY extracts the 'length 11'. The main point is that i really suspect a CodeGuard or a Linker error, because now i'm almost sure that is about the parameter "". That's constant allocated in the space beginning in 0x3C673C (as reported in the line of the .map file that i post already). How hope some of you can support what i believe, analyzing the attachments in news:448ff14a (AT) newsgroups (DOT) borland.com... Thank you, Mauro. "mauro russo" <m.russo (AT) uniplan (DOT) it> ha scritto nel messaggio news:448fefb5 (AT) newsgroups (DOT) borland.com... suspected Code Guard or Linker error!!! In the attached file [on borland.public.attachments] it is showed the screenshot of my pc. Yuo can note that all parameters of the CALL_GDA_EGY that catches the problem are constants (except eax) [eax (0x00 in my case) 0x00, 0x04, 0x003c674d, 0x0a]. So, it means it should be: a) an error of the linker b) an error of "inserting" code of CodeGuard facilities. c) what else? In fact the problem seems to be 0x0a [the message CodeGuard reads 'at 0x003C647D+10...']. You can also note that the problem is catched for the third call to CALL_GDA_EGY. Does it mean that the problem is for the third parameter? [MAX_LENGT_MESSAGES that is a #define (value 127)] or the third-last parameter? [the constant 0]. I hope you can confirm what parameter is it, so i'll concentrate to investigate on only that parameter. In the second attachment i report the following asm-code of the method-call-code and the CodeGuard Window. PS: i'll post the two files on the .attachment newsgroup in some minutes. Thank you to pay attention, Mauro. "Roddy Pratt" <roddy at spam fritter dot com> ha scritto nel messaggio news:448fe42a (AT) newsgroups (DOT) borland.com... "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448fdc92 (AT) newsgroups (DOT) borland.com... CodeGuard got me this weard message. "Attempt to access 4 byte(s) at 0x003C674D+10, that is at offsett 0+10 in block 0x003C674D(=SomeMyDll.DLL:0x02:00674D) which is only 11 bytes long." What can it means "only 11 bytes" if the access is to 4 bytes? "weird" is the spelling you need. It's trying to read 4 bytes at offset 0x10 in a block that is only 11 bytes long. So it IS trying to access outside the block. - Roddy Back to top Pete Fraser Guest Posted: Wed Jun 14, 2006 9:52 pm    Post subject: Re: Weard CodeGuard message You need to show the line of code (in context) which the error occurs in. If you can do this we can tell you whether it is your problem or the linkers/codeguard. Thanks, Pete "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:44903aaf (AT) newsgroups (DOT) borland.com... Quote: "Pete Fraser" <pete.nospam.fraser.nospam (AT) frasersoft (DOT) nospam.net> wrote in the message news:449003eb$1 (AT) newsgroups (DOT) borland.com... What's the line of code where CodeGuard is showing the problem? In the call of method CodeAck. CodeGuard doesn't normally get it wrong - I normally find that I made a mistake. I never told that it gets wrong the number of the line. I told that it gets wrong the error, or that the linker made a mistake. The motivation of my thinking is that Codeguard shows the problem in accessing a constant parameter, that's the const char array "". Pete Mauro Russo. "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448ffd9b (AT) newsgroups (DOT) borland.com... That's the state of my investigation: The parameters are (as documented and as i'm sure you know already) pushed on the stack in the opposite order. The problem is catched for the parameters mess (the empty "" in my case). In fact the address passed is 0x3C6757 that is just 0x3C674D+0x0a. I'll check how CALL_GDA_EGY extracts the 'length 11'. The main point is that i really suspect a CodeGuard or a Linker error, because now i'm almost sure that is about the parameter "". That's constant allocated in the space beginning in 0x3C673C (as reported in the line of the .map file that i post already). How hope some of you can support what i believe, analyzing the attachments in news:448ff14a (AT) newsgroups (DOT) borland.com... Thank you, Mauro. "mauro russo" <m.russo (AT) uniplan (DOT) it> ha scritto nel messaggio news:448fefb5 (AT) newsgroups (DOT) borland.com... suspected Code Guard or Linker error!!! In the attached file [on borland.public.attachments] it is showed the screenshot of my pc. Yuo can note that all parameters of the CALL_GDA_EGY that catches the problem are constants (except eax) [eax (0x00 in my case) 0x00, 0x04, 0x003c674d, 0x0a]. So, it means it should be: a) an error of the linker b) an error of "inserting" code of CodeGuard facilities. c) what else? In fact the problem seems to be 0x0a [the message CodeGuard reads 'at 0x003C647D+10...']. You can also note that the problem is catched for the third call to CALL_GDA_EGY. Does it mean that the problem is for the third parameter? [MAX_LENGT_MESSAGES that is a #define (value 127)] or the third-last parameter? [the constant 0]. I hope you can confirm what parameter is it, so i'll concentrate to investigate on only that parameter. In the second attachment i report the following asm-code of the method-call-code and the CodeGuard Window. PS: i'll post the two files on the .attachment newsgroup in some minutes. Thank you to pay attention, Mauro. "Roddy Pratt" <roddy at spam fritter dot com> ha scritto nel messaggio news:448fe42a (AT) newsgroups (DOT) borland.com... "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448fdc92 (AT) newsgroups (DOT) borland.com... CodeGuard got me this weard message. "Attempt to access 4 byte(s) at 0x003C674D+10, that is at offsett 0+10 in block 0x003C674D(=SomeMyDll.DLL:0x02:00674D) which is only 11 bytes long." What can it means "only 11 bytes" if the access is to 4 bytes? "weird" is the spelling you need. It's trying to read 4 bytes at offset 0x10 in a block that is only 11 bytes long. So it IS trying to access outside the block. - Roddy Back to top mauro russo Guest Posted: Wed Jun 14, 2006 11:06 pm    Post subject: Re: Weard CodeGuard message Just a confirmation. Did you see the attachment i posted on the attachment newsgroup? There i showed the code line in the source (C++) and the asm too. Thank you, Mauro. "Pete Fraser" <pete.nospam.fraser.nospam (AT) frasersoft (DOT) nospam.net> ha scritto nel messaggio news:44903edf (AT) newsgroups (DOT) borland.com... Quote: You need to show the line of code (in context) which the error occurs in. If you can do this we can tell you whether it is your problem or the linkers/codeguard. Thanks, Pete "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:44903aaf (AT) newsgroups (DOT) borland.com... "Pete Fraser" <pete.nospam.fraser.nospam (AT) frasersoft (DOT) nospam.net> wrote in the message news:449003eb$1 (AT) newsgroups (DOT) borland.com... What's the line of code where CodeGuard is showing the problem? In the call of method CodeAck. CodeGuard doesn't normally get it wrong - I normally find that I made a mistake. I never told that it gets wrong the number of the line. I told that it gets wrong the error, or that the linker made a mistake. The motivation of my thinking is that Codeguard shows the problem in accessing a constant parameter, that's the const char array "". Pete Mauro Russo. "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448ffd9b (AT) newsgroups (DOT) borland.com... That's the state of my investigation: The parameters are (as documented and as i'm sure you know already) pushed on the stack in the opposite order. The problem is catched for the parameters mess (the empty "" in my case). In fact the address passed is 0x3C6757 that is just 0x3C674D+0x0a. I'll check how CALL_GDA_EGY extracts the 'length 11'. The main point is that i really suspect a CodeGuard or a Linker error, because now i'm almost sure that is about the parameter "". That's constant allocated in the space beginning in 0x3C673C (as reported in the line of the .map file that i post already). How hope some of you can support what i believe, analyzing the attachments in news:448ff14a (AT) newsgroups (DOT) borland.com... Thank you, Mauro. "mauro russo" <m.russo (AT) uniplan (DOT) it> ha scritto nel messaggio news:448fefb5 (AT) newsgroups (DOT) borland.com... suspected Code Guard or Linker error!!! In the attached file [on borland.public.attachments] it is showed the screenshot of my pc. Yuo can note that all parameters of the CALL_GDA_EGY that catches the problem are constants (except eax) [eax (0x00 in my case) 0x00, 0x04, 0x003c674d, 0x0a]. So, it means it should be: a) an error of the linker b) an error of "inserting" code of CodeGuard facilities. c) what else? In fact the problem seems to be 0x0a [the message CodeGuard reads 'at 0x003C647D+10...']. You can also note that the problem is catched for the third call to CALL_GDA_EGY. Does it mean that the problem is for the third parameter? [MAX_LENGT_MESSAGES that is a #define (value 127)] or the third-last parameter? [the constant 0]. I hope you can confirm what parameter is it, so i'll concentrate to investigate on only that parameter. In the second attachment i report the following asm-code of the method-call-code and the CodeGuard Window. PS: i'll post the two files on the .attachment newsgroup in some minutes. Thank you to pay attention, Mauro. "Roddy Pratt" <roddy at spam fritter dot com> ha scritto nel messaggio news:448fe42a (AT) newsgroups (DOT) borland.com... "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:448fdc92 (AT) newsgroups (DOT) borland.com... CodeGuard got me this weard message. "Attempt to access 4 byte(s) at 0x003C674D+10, that is at offsett 0+10 in block 0x003C674D(=SomeMyDll.DLL:0x02:00674D) which is only 11 bytes long." What can it means "only 11 bytes" if the access is to 4 bytes? "weird" is the spelling you need. It's trying to read 4 bytes at offset 0x10 in a block that is only 11 bytes long. So it IS trying to access outside the block. - Roddy Back to top Roddy Pratt Guest Posted: Thu Jun 15, 2006 1:36 pm    Post subject: Re: Weard CodeGuard message "mauro russo" <m.russo (AT) uniplan (DOT) it> wrote in message news:44905019$1 (AT) newsgroups (DOT) borland.com... Quote: There i showed the code line in the source (C++) and the asm too. < lots of stuff snipped> Mauro, please don't overquote. Codeguard is checking the parameters to your function "CodeAck". Nobody can tell anything much unless you show us the declaration of that method. Also, post the FULL line of code, causing the problem, a screenshot with the source code partially obscured by another window isn't much help. I think you're right that the problem is with the empty string parameter "". I'd hope that CodeAck is expecting a "const char *" for that parameter... - Roddy Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First         BorlandTalk.com Forum Index -> C++ Builder (IDE) All times are GMT Goto page 1, 2, 3, 4  Next Page 1 of 4   Jump to: Select a forum C++ Builder Newsgroups----------------C++ BuilderC++ Builder (ActiveX)C++ Builder (Announcements)C++ Builder (Command Line Tools)C++ Builder DatabasesC++ Builder Databases (ADO)C++ Builder Databases (Desktop)C++ Builder Databases (InterBase Express)C++ Builder Databases (Multi-Tier)C++ Builder Databases (SQL Servers)C++ Builder (Graphics)C++ Builder (IDE)C++ Builder (Internet)C++ Builder (Internet Socket)C++ Builder (Internet Web)C++ Builder (Jobs)C++ Builder (Language)C++ Builder (Language C++)C++ Builder (Compatibility with MFC)C++ Builder (Native API)C++ Builder (Non-Technical)C++ Builder (Students)C++ Builder (Third Party Tools)C++ Builder (Upgrade)C++ Builder (VCL)C++ Builder (VCL Components Usage)C++ Builder (VCL Components Development)C++ Builder (VCL Usage)C++ Builder (WinAPI)C++ Builder Installation Delphi Newsgroups----------------Delphi (General)Delphi ActiveX Controls UsageDelphi ActiveX Controls DevelopmentDelphi As400Delphi DatabasesDelphi Databases (ADO)Delphi Databases (dbExpress)Delphi Databases (Desktop)Delphi Databases (InterBase Express)Delphi Databases (Multi-Tier)Delphi Databases (SQL Servers)Delphi DeploymentDelphi GraphicsDelphi IDEDelphi InternationalizationDelphi InternetDelphi Internet Isapi-WebBrokerDelphi Internet WebSnapDelphi Internet WinsockDelphi JobsDelphi Language BASMDelphi Language ObjectPascalDelphi Model Driven Architecture (General)Delphi Model Driven Architecture (Third Party)Delphi MultimediaDelphi Native APIDelphi Non-TechnicalDelphi ObjectPascalDelphi OLE AutomationDelphi OO designDelphi OpenToolsAPIDelphi Reporting-ChartingDelphi RTLDelphi StudentsDelphi TeamSourceDelphi Thirdparty ToolsDelphi Thirdparty Tools (General)Delphi Thirdparty Tools (IntraWeb)Delphi Thirdparty Tools (RaveReports)Delphi UpgradeDelphi VCLDelphi VCL ComponentsDelphi VCL Components UsingDelphi VCL Components WritingDelphi WebServices SOAPDelphi WinAPIDelphi XMLDelphi Installationcomp.lang.pascal.delphi.components.misccomp.lang.pascal.delphi.components.usagecomp.lang.pascal.delphi.components.writingcomp.lang.pascal.delphi.databasescomp.lang.pascal.delphi.misccomp.sources.delphi JBuilder Newsgroups----------------JBuilderJBuilder AnnouncementsJBuilder Applet IssuesJBuilder As400JBuilder CompilerJBuilder CORBA/RMIJBuilder DatabasesJBuilder DB SwingJBuilder DebuggerJBuilder DeploymentJBuilder DocumentationJBuilder EnterpriseJBuilder HandheldJBuilder IDEJBuilder JavaJBuilder JavaAPIJBuilder Java LanguageJBuilder Java SwingJBuilder Java BeansJBuilder Java Beans UsageJBuilder Java Beans DevelopmentJBuilder JBCLJBuilder JDataStoreJBuilder JobsJBuilder LinuxJBuilder MacintoshJBuilder & MobileSetJBuilder MultiLingual AppsJBuilder Non-TechnicalJBuilder OpenToolsJBuilder Servlets (JSP)JBuilder StudentsJBuilder Team DevelopmentJBuilder Thirdparty ToolsJBuilder UpgradeJBuilder Installation InterBase Newsgroups----------------InterBaseInterBase Bug DiscussionInterBase GeneralInterBase IBConsoleInterBase OpenSourceInterBase ReplicationInterBase SQLInterBase ThirdpartyInterBase Installation Miscellaneous Borland Newsgroups----------------AppCenterAppServerEnteraVisiBroker  You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum Powered by phpBB © 2001, 2006 phpBB Group SEO toolkit © 2004-2006 webmedic.