Getting validation error "argument type mismatch"

I have 2 dropdowns and submit button in jspx page. jspx page has corresponding backing bean with respective properties. When I select values in dropdowns and hit submit I am getting redirected to same page with validation error "argument type mismatch" beneath the dropdowns.

Kate, I bet there is more to the error than you have given here. If I were a betting man I would say it has something to do with the difference between a jbo Number type and the java Number type. I have run into this particular problem twice before. Basically the oracle jbo Number type is not compatible or automatically caste-able into a java type Number. So, perhaps in your backing bean, you have some thing that is defined as a Number in one of jdeveloper's declaritive fields (jbo Number) and in a java program somewhere you have probably declared a variable as just plain-old Number which is a different class...coming from Java's built-in types classes.
Hope that's your problem, and I hope this helps.
Michael F.

Similar Messages

  • ByRef Argument Type Mismatch" Error VB6

    I am new to VB6 and spread.My VB project is making using of spread .In forms wherever the spread initialization is done,VB 6 is throwing a compile error as "By Ref Argument Type Mismatch" Error" .Is it because of the spread issue? I am removing
    some functionality from a already existing vb project So is it because i might have commented out some functionality. Kindly.Kindly provide your valuable suggestion.Thanks in advance.I am running the application in windows 7

    Hi ponnudoll,
    This forum is actually for questions about Access development, your question is kind of off-topic.
    Where to post your VB 6 questions
    Anyway, I did some research about this error message, and found this KB article talking about how to avoid this error.
    How to Avoid the "ByRef Argument Type Mismatch" Error
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Flex 4.5 - java.lang.IllegalArgumentException: argument type mismatch

    0 down vote favorite
    I am having a problem when sending a soap request from a flex  4.5 application to a coldfusion 9 web service created using a CFC.
    The  most annoying thing it is only an intermittent problem but I can't work  out what is wrong.
    There a many methods within the web service of which Flex has no  issue, but these are mainly ones that read data.  The one I am having a  problem with is one that is writing back to the web service.
    The issue only arises when I have to restart the Coldfusion service  for some reason, which is quite often as the development machine is my  laptop.  It has now also happened when I have moved the Flex app to a  development server for testing and as it's hosted I can't restart the  services easily.
    I get the response below every time.  I have tried tracing the call  through the Flash Builder Network monitor and building a dummy call  using the same data, all to no avail.
    I have tried stripping out all of the code and then rebuilding it,  which takes a long time as I am using custom types in ColdFusion.
    Also , if I cfinvoke the method through a CFM page, it works fine. It  is only when trying to call it through a SOAP request through Flex 4.5.
    It will then suddenly start working again however and then it is fine  until I restart the CF services again.
    I can't tell what I triggers it  to start working again.
    Does something initialise it in ColdFusion and then it's fine ???.  I am  really struggling with this and any help would be appreciated.
    I have a  sample SOAP request that I trapped in the Network Monitor and also the  WSDL if needed.
    java.lang.IllegalArgumentException: argument type mismatch
        <ns1:stackTrace xmlns:ns1="http://xml.apache.org/axis/"
        xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">java.lang.IllegalArgumentException: argument type mismatch
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.axis.utils.BeanPropertyDescriptor.set(BeanPropertyDescriptor.java:142)
    at org.apache.axis.encoding.ser.BeanPropertyTarget.set(BeanPropertyTarget.java:75)
    at org.apache.axis.encoding.DeserializerImpl.valueComplete(DeserializerImpl.java:249)
    at org.apache.axis.encoding.DeserializerImpl.endElement(DeserializerImpl.java:509)
    at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
    at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:171)
    at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
    at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
    at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
    at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:148)
    at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
    at coldfusion.xml.rpc.CFCProvider.invoke(CFCProvider.java:54)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453)
    at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
    at coldfusion.xml.rpc.CFCServlet.doAxisPost(CFCServlet.java:270)
    at coldfusion.filter.AxisFilter.invoke(AxisFilter.java:43)
    at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:356)
    at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)
    at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
    at coldfusion.filter.PathFilter.invoke(PathFilter.java:87)
    at coldfusion.filter.LicenseFilter.invoke(LicenseFilter.java:27)
    at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)
    at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
    at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
    at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
    at coldfusion.xml.rpc.CFCServlet.invoke(CFCServlet.java:138)
    at coldfusion.xml.rpc.CFCServlet.doPost(CFCServlet.java:289)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
    at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
    at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42)
    at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
    at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
    at jrun.servlet.FilterChain.service(FilterChain.java:101)
    at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
    at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
    at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
    at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
    at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
    at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
    at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
    at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
    at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)</ns1:stackTrace>
    <ns2:hostname xmlns:ns2="http://xml.apache.org/axis/" xmlns:soapenv
    ="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org2001/XMLSchema-instance">Darren-LT</ns2:hostname>

    Someone suggested it could be a serialisation issue but I I'm not sure how to go about checking that.
    Any suggestions ?

  • ClassLoader "argument type mismatch" problem

    I've got a problem I was hoping someone would be able to help me out with, or at least explain why I'm getting the problem.
    Here's the scenario:
    *I've got an abstract class, BETI public abstract class BETI*I've got another class, TMPC, which extends BETI and implements others.
    public class TMPC extends BETI implements .....*I've got a third class ABT, which has a method that looks like:
    public void addListener(BETI _listener);*In a fourth class, I've been able to successfully load ABT, but I'm having problems invoking the addListener method.
    Here's the segment:
    Class customLoggerClass = classLoader.loadClass("blah.ABT");
    Object customLogger = customLoggerClass.newInstance();
    TMPC gui = new TMPC();
    Object[] oneArgument = new Object[1];
    Class beti = classLoader.loadClass("blah.BETI");
    Class[] addBuildListenerParameters = {beti};
    Method addBuildListenerMethod = customLoggerClass.getMethod("addBuildListener",addBuildListenerParameters);
    oneArgument[0] = gui;
    addBuildListenerMethod.invoke(customLogger,oneArgument); //here is where the argument type mismatch happensAny idea on why I'm getting this? Obviously I'm overlooking something simple, but....
    Thanks in advance-

    Presuming I did it right...
    Using
    c0 = default loader
    c1 = your loader
    >
    Object customLogger =
    customLoggerClass.newInstance();
    TMPC gui = new TMPC();This loads c0.BETI and c0.TMPC
    Object[] oneArgument = new Object[1];
    Class beti = classLoader.loadClass("blah.BETI");I bet this loads c1.BETI
    Class[] addBuildListenerParameters = {beti};
    Method addBuildListenerMethod =
    customLoggerClass.getMethod("addBuildListener",addBuild
    istenerParameters);
    oneArgument[0] = gui;
    addBuildListenerMethod.invoke(customLogger,oneArgument)
    //here is where the argument type mismatch happensSo here the signature is
    addBuildListener(c1.BETI)
    and you are calling it with
    addBuildListener(c0.TPMC)
    And that can only resolve to c0.BETI which doesn't match.

  • RisPort problems - argument type mismatch

    Hi!
    I'm trying to get a list of devices via RisPort. I copied example from http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/5_0/ccmdev/ccmdvch2.htm chapter Real-Time Information (RisPort)
    Selecting Cisco Unified CallManager Real-Time Information , but service returning following xml:
    <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.IllegalArgumentException: argument type mismatch</faultstring><detail><ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">CUCM6</ns1:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
    And my question is: How can I recognize, which argument? There are no any notes or details :-(
    Many thanks for your ideas!!
    ps. or is it posible to get that list any other way? (CUM6)

    check your gmail~i sent my code to your email!
    here is the xml String:
    String strSoapMsg="<?xml version=\"1.0\" encoding=\"utf-8\"?>"+
    "http://schemas.xmlsoap.org/soap/envelope/\" "+
    "xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" "+
    "xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">"+
    ""+
    "http://schemas.xmlsoap.org/soap/encoding/\">"+
    ""+
    ""+
    ""+
    "http://schemas.xmlsoap.org/soap/encoding/\" "+
    "xsi:type=\"ns1:CmSelectionCriteria\" xmlns:soapenc=\"http://schemas.xmlsoap.org/soap/encoding/\" "+
    "xmlns:ns1=\"tns:CmSelectionCriteria\">"+
    "2000"+
    ""+
    "Name"+
    ""+
    ""+
    ""+
    ""+

  • MS VB Run-Time Error '13': Type Mismatch

    Hi,
    I'm new to the forum, and just starting a trial of RH7 as my
    company decides whether we'll upgrade from our X4 product or switch
    to a different HAT. Before attempting to import my existing HPJ
    project, I opened the sample Application Help project. Frequently
    when I switch among topics, I get a Microsoft Visual Basic dialog
    box that says Run-Time Error '13': Type Mismatch. I have to click
    the End button to close the dialog box. Does anyone have any idea
    what causes the error? I got that error also in X4 when switching
    among topics in my own project (on a different computer).

    Hello Brian,
    I'm thrilled!!! Your clue was enough to set me in the right
    direction, so after spending many hours searching for the solution
    to this problem lately and in the past, it appears to finally be
    solved. Initially just unchecking the other add-ins didn't do the
    trick, and the situation seemed to get worse and worse--I couldn't
    save files because Word kept giving me error messages that macros
    were disabled (which I didn't know how to rectify), and RH kept
    freezing. I noticed after a while that the RoboHelp menu in Word
    would have disappeared when RH froze, and that the template would
    have changed to Normal.dot. If I reattached the RoboHelp.dot
    template, RH would unfreeze, but later the template would switch
    back to Normal and RH would freeze again. I was initimidated to
    edit the registry. Finally I came upon this page
    http://personal-computer-tutor.com/NNTWord.htm
    where the author Linda gave the path to the Word startup folder
    where I found some templates whose filenames were preceded by
    tildes (corrupt?). I deleted those and other junk and I temporarily
    deleted the normal.dot template at Linda's suggestion. Since then,
    the run-time errors have no longer occurred and the other problems
    have not recurred. I THINK I'm back on track! I'm thrilled because
    my boss encouraged me to uninstall and re-install Office and
    migrate to different HAT, a time-consuming process I'd rather avoid
    at least until the current release is completed. Thank you so much
    for your help!!

  • Run Time Error '13' Type Mismatch in SAP BEx

    Hello, SAP World!
    If i try to see "Query Properties" in Excel 2007 in BEx Analyzer, getting the error:
    Run-time error '13'
    Type Mismatch.
    Plz, Help!
    For Excel 2003 this error is not occured.
    GUI 6.40
    File Ver. 6405.5.27.3058
    Patch Level: 27
    SAP BW 3500.4.020

    are you using BW 3.5 or 7.0 (BI nw2004as) ?
    have you installed both BW add-on (3.5 and 7.0) ?

  • No message for validation error "format", type "date", field "date-expired"

    Dear
    Guys,
    i am getting the following error : ((No message for validation error "format", type "date", field "date-expired"))
    When trying to upload adobe connect 7 license to the adobe connect 7 configuration wizard. the problem occurs because my server was install on Arabic Saudi Arabia date format while installation, but if i change the windows date format to US then the problem still occurs, and formatting windows is not possible, could anybody help??
    Regards

    Thank you for replying,
    No i am not on host mode, a have installed it deferent times ago successfully, but the only problem now is that during the installation windows server 2008 the default language, time and date. Was set Arabic Saudi Arabia. And even changing it does not solve the problem, as i mentioned above.

  • Run-time error '13':  Type mismatch

    There are A and B excel files.
    And two different POV-dimension in two excel files
    VBA code below:
    Dim vtGrid As Variant
    Dim vtDimNames As Variant
    Dim vtPOVNames As Variant
    x = HypRetrieve("sheet1")
    x = HypUseLinkMacro(True)
    Range("b10").Select
    x = HypGetSourceGrid("sheet1", vtGrid)
    ref = HypMenuVRefresh()
    x = HypGetPOVItems(vtDimNames, vtPOVNames)
    MsgBox (vtPOVNames(6))
    Range("a3").Value = "date: " & vtPOVNames(6) & " - " & vtPOVNames(3)
    Range("a4").Value = "dep : " & vtPOVNames(0)
    There is not any attribute dimension in pov A excel file.
    There is one attribute dimension in pov B excel file.
    The same VBA code excute is normal in A excel file.
    But the same VBA code excute is "run-time error '13': Type mismatch " in B excel file.
    The error '13' in the row of MsgBox (vtPOVNames(6)).
    Is attribute dimension in pov cause this question?
    And how did I solve this question?

    Based on where the error is occurring, it looks like the value returned by vtPOVNames(6) is not defaulting to a string datatype for the msgbox.
    Try 'cstr(vtPOVNames(6))' to force conversion of the value into a string. Also, you may want to test for nulls using IsNull() and empty variant values using IsEmpty().
    It doesn't look like the code you posted shows vtPOVNames being populated. If you're populating the names yourself, you could always use a string array instead of a variant array. Just dim the string array using a statement such as, "Dim strPOVNames(6) as String" or "Dim strPOVNames() as String" in case you need to ReDim the array later to size it for a non-fixed set of POV names.
    Hope this helps.

  • Bex : Run-time Error '13' - Type Mismatch

    Dear,
    I have a trouble with BEX. With some user, they can not start BEX.
    When They start BEX, they have the Run-Time Error '13'  type mismatch.
    With a administrator account, we have not problem.
    When I go in the debug, it stop on "addIn.RunAutoMacros (xlAutoOpen)"
    Could you help me ?
    Thank you,
    Philippe Dupriez

    Phillipe, did you solve this issue. I have a similar issue
    AddIn.RunAutoMacros(xlAutoOpen).
    I appreciate your reply.
    Thanks,
    Parvathi.

  • SBO Run-time error '13' Type mismatch

    Hello,
    I'm currently using SBO 2005 SP1 (PL11)
    After installing SBO DTW (2005A PL11 as well), i'm facing this issue : Run-time Error '13' Type mismatch
    I've been trying to modify my regional settings as per the previous discussions but this didn't work (first of all, i'm located in France, and try to apply the french regional settings).
    I've uninstalled and reinstalled DTW and my DI API but unfortunately, this didn't"t work either.
    Any other advise on this problem ?
    Thanks,
    Stephane

    Stephane,
    Here are some links to SAP Notes on the SAP PartnerEdge Portal that may help.  Please read the note carefully as the first note has your remove the Windows User Profile.
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0000873864
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0000884234
    If these do not help I recommend that you log a message with SAP Technical Support as the forum you have posted your question in is for questions related to the SAP Business One SDK and your question is application related to the DTW.
    HTH,
    Eddy

  • Getting Validation Error at B2B Console for 856 Outbound B2B-51507

    Hi,
    We are getting this error while sending the EDI 856 in an outgoing Process. We are getting the data from Oracle Apps and sending it to B2B via B2b adapter using mediator.
    we are using X856 ecx file and X856 xsd.
    Can Anyone help in this. If Anyone is having any idea please help us on this.
    Do we need to set the Deployment Validation Property to False? If yes then is it in EM we need to Set?
    Appreciate quick response.
    Below is the error details:
    Id 0AF6038D12BE3AE21CF0000011881680
    Message Id 0AF6038D12BE3AE1C5E0000011881630
    Refer To Message Refer To Message
    Sender Type Specialties
    Receiver Type Name
    Receiver Value XXXX_4010
    Sender Sybron Dental Specialties
    Receiver :XXXX_4010
    Agreement Id:XXXXXXX
    Agreement HEN_KRR_AGR
    Document Type 856
    Document Protocol EDI_X12
    Document Version 4010
    Message Type REQ
    Direction OUTBOUND
    State MSG_ERROR
    Acknowledgement Mode NONE
    Response Mode NONE
    Send Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
    Receive Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
    Document Retry Interval 0
    Document Remaining Retry 0
    Native Message Size
    Translated Message Size 3811
    Business Action Name
    Business Transaction Name
    Xpath Name1 XPathName1
    Xpath Value1
    Xpath Expression1
    Xpath Name2 XPathName2
    Xpath Value2
    Xpath Expression2
    Xpath Name3 XPathName3
    Xpath Value3
    Xpath Expression3
    Correlation From XPath Name CorrelationFromXPathName
    Correlation From XPath Value
    Correlation From XPath Expression
    Correlation To XPath Name CorrelationToXPathName
    Correlation To XPath Value
    Correlation To XPath Expression
    Wire Message Wire Message
    Application Message Application Message
    Payload Storage Payload Storage
    Attachment Attachment
    Label soa_b2b_ - Fri Oct 22 04:32:37 PDT 2010
    Collaboration Id 0AF6038D12BE3AE205B0000011881670
    Collabration Name
    Collabration Version
    Business Action Name
    Exchange Protocol Name Generic File
    Exchange Protocol Version 1.0
    Interchange Control Number
    Group Control Number
    Transaction Set Control Number
    Error Code B2B-51507
    Error Description Machine Info: (org-vmsosoa.sds.sybrondental.com) Description: Payload validation error.
    Error Level ERROR_LEVEL_COLLABORATION
    Error Severity ERROR
    Error Text Error Brief : XEngine error.
    This is the Application Message we are getting in Error Details:
    Document Type 856
    Document Definition 856_DocDefHENK
    Document Protocol Name EDI_X12
    Document Protocol Version 4010
    Refer To Application Message Id Refer To Application Message Id
    App Conversation Id
    App Message property {tracking.compositeInstanceId=11, b2b.documentProtocolVersion=4010, b2b.toTradingPartnerId=HEN_KRR_4010, tracking.ecid=0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz, b2b.fromTradingPartnerId=Sybron Dental Specialties, tracking.conversationId=BPEL, tracking.compositeInstanceCreatedTime=Mon Oct 25 06:57:39 PDT 2010, tracking.parentComponentInstanceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492, MESH_METRICS=null, b2b.documentTypeName=856, tracking.parentReferenceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492:D4AC5730E03F11DFBFC66D8172AE9492:oneway}
    Direction OUTBOUND
    State MSG_ERROR
    Error Code B2B-51507
    Error Text Error Brief : XEngine error.
    Error Description Error : Mandatory attribute missing: Standard.
    Created Date Monday, October 25, 2010 6:57:40 AM GMT-07:00
    Modified Date Monday, October 25, 2010 6:57:41 AM GMT-07:00
    Message Size 3811
    Payload Payload
    Business Message Business Message
    Retry Interval 0
    Reattempt Count 0
    Remaining Retry 0
    ECID 0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz
    Composite Instance Id 11
    Parent Composite Instance Id mediator:D4A7EA60E03F11DFBFC66D8172AE9492
    Conversation Id BPEL
    Domain Name default
    Composite Name Generate856ASNOutbound
    Composite Version 2.0
    Reference Name B2B_GetData

    Hi,
    It looks like , Payload is not valid as per the ecs/xsd so B2B is giving Payload validation Error.
    If Validation is must then validate the payload against ecs/xsd offline and correct.
    or you can turn off validation in Agreement (Validation = false) and redeploy the agreement.
    Rgds,
    Nitesh Jain

  • Running KE27. Getting an error " Condition type XX12 is not active"

    Hi There -
    When running KE27 getting an error Copa Validation:  Condition Type XX12 is not active.
    Appreciate your time.
    Thanks
    Sri

    Hi Sri,
    is this a standard erromessage? Which code (ex: XY123)?
    br, Guido

  • SSI Validation Error: doc type does not allow styles element in body of page

    When I validate my index page with wc.org, I get 2 errors regarding having styles elements h1-h6 in the body vs the head of the page.  My Nav and Footer are SSIs and I have used styles h1-h6 on them.
    Q.  Should I delete the h1-h6 styles from the beginning code of the Nav.htm and Footer.htm?
    Q.  If I delete that code, will they use the styles.css inserted in the head code of each pate?
    Thanks.

    The problem is this block of code belongs in the Head of yoru page, not in a TD  in the Body!  And you also have it below in the Footer.  So now I understand better yoru 2 original quesitons.  Yes, but htis code only in the Head of the page and it will work for the entire page, even for html inserted via Includes.  So remove this style block from all yoru Includes unless some fo them are designed to write into the Head of the page only.
    <style type="text/css">
    <!--
    h1 {
         font-family: Arial, Helvetica, sans-serif;
         font-size: 16px;
         font-weight: bold;
         color: #008000;
    h2 {
         font-family: Arial, Helvetica, sans-serif;
         font-size: 16px;
         font-style: italic;
         font-weight: bold;
         color: #E3372E;
    h3 {
         font-family: Arial, Helvetica, sans-serif;
         font-size: 16px;
         font-weight: bold;
         color: #AB003C;
    h4 {
         font-family: Arial, Helvetica, sans-serif;
         font-size: 16px;
         font-style: italic;
         font-weight: bold;
         color: #E62B86;
    h5 {
         font-family: Arial, Helvetica, sans-serif;
         font-size: 14px;
         font-style: italic;
         font-weight: bolder;
         color: #E3372E;
    h6 {
         font-family: Arial, Helvetica, sans-serif;
         font-size: 18px;
         font-weight: bold;
         color: #AB003C;
    -->
    </style>
    Or even better would be to put this into an external style sheet that
    all your pages can call (not the Includes, just the "real" pages!
    E. Michael Brandt
    www.divahtml.com
    www.divahtml.com/products/scripts_dreamweaver_extensions.php
    Standards-compliant scripts and Dreamweaver Extensions
    www.valleywebdesigns.com/vwd_Vdw.asp
    JustSo PictureWindow
    JustSo PhotoAlbum, et alia

  • "Error 13 type mismatch" appears in a VB6 under XP but not under wWindows 2000 ...

    Hello !
    I would like to use Daqmx functions in a VB6 program I am currently writing. In order to gain ideas about how to do it, I ran an example code DigPulseTrain-Cont.vbp included in Labview 8.2 intsallation. It works OK when ran on a Window 2000 PC, but delivers an arror massage "13 Type mismatch" when using a XP platform. Is it documented somewhere and any fix I can use to bypass this ?
    Thank you !
    Nicolas GINET

    Hi,
    Here there is an explanation of this type of error:
    http://digital.ni.com/public.nsf/allkb/8800DECF0D358C9D86256B1700656C04?OpenDocument
    Regards.

Maybe you are looking for