Rowid and urowid datatypes

I'm writing an exercise to learn more about different datatypes and am confused about the use of and difference between rowid and urowid. As I understand it using rowid should only be done when writing for backwards compatibility, and urowid should be used for new coding. I'm working in 9.2.0.1.0, so I assume I should use urowid.
The following code returns an error (shown below). Anyone know why this is happenning?
create or replace function lrnvrbls
return varchar2
is
v_rowid urowid;
v_data varchar2(100);
select rowid
into v_rowid
from mytable
where rownum = 10 -- 10 is just a number I chose
execute immediate
'select mycolumn ' ||
'from mytable ' ||
'where rowid = ' ||
v_rowid
into v_data;
return v_data;
end;
SQL>select lrnvrbls from dual;
select lrnvrbls from dual
ORA-00904: "AAAHCAAAMAAAADVAAI": invalid identifier
I've tried using both ROWID and UROWID datatypes with no luck. Also tried CHARTOROWID and ROWIDTOCHAR and failed the same way.
Anybody understand how to use this?

A single datatype called the universal rowid, or UROWID, supports both logical
and physical rowids, as well as rowids of foreign tables such as non-Oracle
tables accessed through a gateway.
A column of the UROWID datatype can store all kinds of rowids. The value of the
COMPATIBLE initialization parameter must be set to 8.1 or higher to use UROWID
columns.
DROP TABLE mytable
CREATE TABLE mytable
AS SELECT owner mycolumn FROM all_tables
WHERE rownum < 100
CREATE OR REPLACE
FUNCTION lrnvrbls
RETURN varchar2
IS
v_rowid urowid;
v_data varchar2(100);
strSQL varchar2(255);
BEGIN
select rowid
into v_rowid
from mytable
where rownum = 1;
strSQL := 'select mycolumn from mytable where rowid = '''||v_rowid ||'''';
execute immediate strSQL into v_data;
return v_data;
END lrnvrbls;
SELECT lrnvrbls FROM DUAL
DROP FUNCTION lrnvrbls
DROP TABLE mytable
COMMIT
16:39:37 SQL> DROP TABLE mytable
16:39:39 2 /
Table dropped.
Elapsed: 00:00:00.00
16:39:39 SQL> --
16:39:39 SQL> CREATE TABLE mytable
16:39:39 2 AS SELECT owner mycolumn FROM all_tables
16:39:39 3 WHERE rownum < 100
16:39:39 4 /
Table created.
Elapsed: 00:00:00.00
16:39:39 SQL> --
16:39:39 SQL> CREATE OR REPLACE
16:39:39 2 FUNCTION lrnvrbls
16:39:39 3 RETURN varchar2
16:39:39 4 IS
16:39:39 5 --
16:39:39 6 v_rowid urowid;
16:39:39 7 v_data varchar2(100);
16:39:39 8 strSQL varchar2(255);
16:39:39 9 --
16:39:39 10 BEGIN
16:39:39 11 --
16:39:39 12 select rowid
16:39:39 13 into v_rowid
16:39:39 14 from mytable
16:39:39 15 where rownum = 1;
16:39:39 16 --
16:39:39 17 strSQL := 'select mycolumn from mytable where rowid = '''||v_rowid ||'''';
16:39:39 18 --
16:39:39 19 execute immediate strSQL into v_data;
16:39:39 20 --
16:39:39 21 return v_data;
16:39:39 22 --
16:39:39 23 END lrnvrbls;
16:39:39 24 /
Function created.
Elapsed: 00:00:00.00
16:39:39 SQL> --
16:39:39 SQL> SELECT lrnvrbls FROM DUAL
16:39:39 2 /
LRNVRBLS
SYS
Elapsed: 00:00:00.00
16:39:39 SQL> --
16:39:39 SQL> DROP FUNCTION lrnvrbls
16:39:39 2 /
Function dropped.
Elapsed: 00:00:00.01
16:39:40 SQL> DROP TABLE mytable
16:39:40 2 /
Table dropped.
Elapsed: 00:00:00.00
16:39:40 SQL> COMMIT
16:39:40 2 /
Commit complete.
Elapsed: 00:00:00.00
16:39:40 SQL>
*/

Similar Messages

  • How to get the rowid and the entire record selected in PLSQL?

    The code given below does not work.
    You cannot select the record and the rowid using a cursor in one-shot.
    But you could do that in a direct SELECT in "SQL Plus" when you select records for display. Is this a bug in ORACLE PLSQL? Or is there another way to do this?
    DECLARE
    objid_ VARCHAR2(200);
    rec_ xxx_tab%ROWTYPE;
    CURSOR get_rec IS
    SELECT t.*, t.rowid
    FROM xxx_tab t;
    BEGIN
    OPEN get_rec;
    FETCH get_rec INTO rec_, objid_;
    CLOSE get_rec;
    END;
    -----------------------------------

    You cannot fetch into both a record type and a variable. You have a few options, you can declare the record a s a rowtype of the cursor like this:
    DECLARE
       CURSOR c IS
          SELECT t.*, rowid rid
          FROM t;
       l_rec c%ROWTYPE;
    BEGIN
       OPEN c;
       FETCH c INTO l_rec;
       CLOSE c;
    END;You could use an implicit cursor and let Oracle deal with the record type internally (not to mention the open fetch and close) like this:
    BEGIN
       FOR rec in (SELECT t.*, rowid rid FROM t) LOOP
          do_stuff with rec.col_name
       END LOOP;
    END;Note that in both of these you must alias the rowid column to some other name, you could also manually construct the record type to match the table and add a column od ROWID datatype to hold the rowid.
    Finally, I think, depending on what you are actually going to do with the rowid, and how you feel about having records locked, you could look at declaring the cursor as FOR UPDATE and get rhe rowid for free.. This would be most appropriate if you are planning to update the table in the cursor (a bad practce by the way). Something like:
    DECLARE
       l_rec t%ROWTYPE;
       CURSOR c IS
          SELECT t.*, rowid
          FROM t;
    BEGIN
       OPEN c;
       FETCH c INTO l_rec;
       do_whatever with l_rec
       UPDATE t
       SET whatever
       WHERE current of c;
    END;John

  • Difference between CHAR and VARCHAR2 datatype

    Difference between CHAR and VARCHAR2 datatype
    CHAR datatype
    If you have an employee name column with size 10; ename CHAR(10) and If a column value 'JOHN' is inserted, 6 empty spaces will be inserted to the right of the value. If this was a VARCHAR column; ename VARCHAR2(10). How would it handle the column value 'JOHN' ?

    The CHAR datatype stores fixed-length character strings, and Oracle compares CHAR values using blank-padded comparison semantics.
    Where as the VARCHAR2 datatype stores variable-length character strings, and Oracle compares VARCHAR2 values using nonpadded comparison semantics.
    This is important when comparing or joining on the columns having these datatypes;
    SQL*Plus: Release 10.2.0.1.0 - Production on Pzt Au 6 09:16:45 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    SQL> conn hr/hr
    Connected.
    SQL> set serveroutput on
    SQL> DECLARE
    2 last_name1 VARCHAR2(10) := 'TONGUC';
    3 last_name2 CHAR(10) := 'TONGUC';
    4 BEGIN
    5 IF last_name1 = last_name2 THEN
    6 DBMS_OUTPUT.PUT_LINE ( '-' || last_name1 || '- is equal to -' || last_name2
    || '-');
    7 ELSE
    8 DBMS_OUTPUT.PUT_LINE ( '-' || last_name1 || '- is NOT equal to -' || last_n
    ame2 || '-');
    9 END IF;
    10 END;
    11 /
    -TONGUC- is NOT equal to -TONGUC -
    PL/SQL procedure successfully completed.
    SQL> DECLARE
    2 last_name1 CHAR(6) := 'TONGUC';
    3 last_name2 CHAR(10) := 'TONGUC';
    4 BEGIN
    5 IF last_name1 = last_name2 THEN
    6 DBMS_OUTPUT.PUT_LINE ( '-' || last_name1 || '- is equal to -' || last_name2
    || '-');
    7 ELSE
    8 DBMS_OUTPUT.PUT_LINE ( '-' || last_name1 || '- is NOT equal to -' || last_n
    ame2 || '-');
    9 END IF;
    10 END;
    11 /
    -TONGUC- is equal to -TONGUC -
    PL/SQL procedure successfully completed.
    Also you may want to read related asktom thread - "Char Vs Varchar" http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:1542606219593
    and http://tahitiviews.blogspot.com/2007/05/less-is-more-more-or-less.html
    Best regards.

  • How to copy a table with LONG and CLOB datatype over a dblink?

    Hi All,
    I need to copy a table from an external database into a local one. Note that this table has both LONG and CLOB datatypes included.
    I have taken 2 approaches to do this:
    1. Use the CREATE TABLE AS....
    SQL> create table XXXX_TEST as select * from XXXX_INDV_DOCS@ext_db;
    create table XXXX_TEST as select * from XXXX_INDV_DOCS@ext_db
    ERROR at line 1:
    ORA-00997: illegal use of LONG datatype
    2. After reading some threads I tried to use the COPY command:
    SQL> COPY FROM xxxx/pass@ext_db TO xxxx/pass@target_db REPLACE XXXX_INDV_DOCS USING SELECT * FROM XXXX_INDV_DOCS;
    Array fetch/bind size is 15. (arraysize is 15)
    Will commit when done. (copycommit is 0)
    Maximum long size is 80. (long is 80)
    CPY-0012: Datatype cannot be copied
    If my understanding is correct the 1st statement fails because there is a LONG datatype in XXXX_INDV_DOCS table and 2nd one fails because there is a CLOB datatype.
    Is there a way to copy the entire table (all columns including both LONG and CLOB) over a dblink?
    Would greatelly appriciate any workaround or ideas!
    Regards,
    Pawel.

    Hi Nicolas,
    There is a reason I am not using export/import:
    - I would like to have a one-script solution for this problem (meaning execute one script on one machine)
    - I am not able to make an SSH connection from the target DB to the local one (although the otherway it works fine) which means I cannot copy the dump file from target server to local one.
    - with export/import I need to have an SSH connection on the target DB in order to issue the exp command...
    Therefore, I am looking for a solution (or a workaround) which will work over a DBLINK.
    Regards,
    Pawel.

  • What is the difference between logical ROWID and physical ROWID

    hello
    can u please explain the difference between logical ROWID and physical ROWID
    regards,

    from the docs (a 30 sec search)
    Physical rowids store the addresses of rows in ordinary tables (excluding index-organized tables), clustered tables, table partitions and subpartitions, indexes, and index partitions and subpartitions.
    Logical rowids store the addresses of rows in index-organized tables.

  • What are ROWID and ROWNUM? Are they stored in database and where?

    Hi All,
    can anybody please answer this question
    What are ROWID and ROWNUM? Are they stored in database and where?
    Thanks,
    Srini

    ROWID can be thought of as a pointer to the physical location (on disk) of the (table) row.
    From a ROWID value, Oracle can extract the file, block-within-that-file and offset-of-the-row-within-that-block. Using these, Oracle can directly access a disk block to retrieve a row.
    ROWNUM is a just sequence number of a row within a result set of a query.
    As said by other repliers, both are not stored. They are 'constructed' when you reference them inside a query.

  • Export and Import Of Tables having BLOB and Raw datatype

    Hi Gurus,
    I had to export one schema in one database and import to another schema in another database.
    However my current database contains raw and blob datatype.I have exported the whole database by the following commnad
    exp SYSTEM/manager FULL=y FILE=jbrms_full_19APR2013.dmp log=jbrms_full_19APR2013.log GRANTS=y ROWS=y
    My question is if all the tables with raw and blob have been exported properly or not.I have done one more thing after taking the export , I have imported to local db and checked the no of rows in the both the envs are same.As I have not tested with the application to confirm.
    I am using this version of Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    not able to attach the complete log file but for the schema jbrms which has the blob and raw datatype.
    Please let me know if you find some potential concerns with the export for BLOB and raw
    . about to export JBRMS's tables via Conventional Path ...
    . . exporting table FS_FSENTRY 8 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table FS_WS_DEFAULT_FSENTRY 2 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table PM_WS_DEFAULT_BINVAL 60 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table PM_WS_DEFAULT_BUNDLE 751 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table PM_WS_DEFAULT_NAMES 2 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table PM_WS_DEFAULT_REFS 4 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table VERSIONING_FS_FSENTRY 1 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table VERSIONING_PM_BINVAL 300 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table VERSIONING_PM_BUNDLE 11654 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table VERSIONING_PM_NAMES 2 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.
    . . exporting table VERSIONING_PM_REFS 1370 rows exported
    EXP-00091: Exporting questionable statistics.
    EXP-00091: Exporting questionable statistics.

    You could see the 'QUESTIONABLE STATISTICS' warning for a couple of reasons. I don't remember them all but.
    1. If the target and source character set is different.
    2. system generated names (I think?)
    the best solution if you don't need the exact statistics that are on your source database would be to add
    statistics=none
    to your imp command and then regather statistics when the imp command is done.
    Dean

  • How we handle CLOB and BLOB Datatypes in HANA DB

    Dear HANA Gurus,
    We have would like to build EDW using HANA base on our source system Oracle and it's supports CLOB and BLOB datatypes
    Would you please suggest how do we handle in HANA DB.
    Let not say it's oracle specific.
    Regards,
    Manoj

    Hello,
    check SAP HANA SQL Reference Guide for list of data types:
    (page 14 - Classification of Data Types)
    https://service.sap.com/~sapidb/011000358700000604922011
    For this purpose might be useful following data types:
    Large Object (LOB) Types
    LOB (large objects) data types, CLOB, NCLOB and BLOB, are used to store a large amount of data such as text documents and images. The maximum size of an LOB is 2 GB.
    BLOB
    The BLOB data type is used to store large binary data.
    CLOB
    The CLOB data type is used to store large ASCII character data.
    NCLOB
    The NCLOB data type is used to store a large Unicode character object.
    Tomas

  • VALIDATE_LAYER_WITH_CONTEXT - Rowid and NULL in result table

    Hello,
    Oracle 10g R2
    I performed validity test using VALIDATE_LAYER_WITH_CONTEXT as follow:
    CREATE TABLE RESULT_TABLE_CP(SDO_ROWID ROWID, RESULT VARCHAR2(2000));
    CALL SDO_GEOM.VALIDATE_LAYER_WITH_CONTEXT('VESSEL_ZONE_GEOMETRY', 'POLYGON', 'RESULT_TABLE_CP');
    What puzzled me was the result table contained the rowid and NULL as the result for each geometry. I was expecting to see what the error is, not just NULL.
    However when I use VALIDATE_GEOMETRY_WITH_CONTEXT to test the same layer, I got TRUE for all of them, as:
    select DISTINCT SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(a.POLYGON,b.DIMINFO)
    from VESSEL_ZONE_GEOMETRY a,
    USER_SDO_GEOM_METADATA b
    where b.TABLE_NAME = 'VESSEL_ZONE_GEOMETRY'
    and b.COLUMN_NAME = 'POLYGON'
    and a.POLYGON is not null;
    SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT(A.POLYGON,B.DIMINFO) ------------------------------------------------------------------------------------
    TRUE
    Any suggestion would be much appreciated!
    Thanks, CP

    Can you get the geometry by running
    select polygon from VESSEL_ZONE_GEOMETRY where rowid = '....';

  • Help changing all PK and FK datatypes from uniqueidentifier to nvarchar(128)

    Is there a simple script to iterate through all my tables and change my PK and FK datatypes to nvarchar(128)? I don't want to have to go through each table manually, remove relationships, and change each key one by one. Here is my db schema if it helps.

    Hi Man_Cat,
    According to your description, you are looking for the script to update all the PK and FK datatypes from uniqueidentifier to nvarchar(128), right?
    Based on my research, we cannot change the data type of the Primary Key and Foreign Key directly as Tom said. However, we can drop the PK and FK and recreate them use the query below.
    --This will drop the primary key temporarily
    ALTER TABLE MyTable
    drop CONSTRAINT PK_MyTable
    --change data type
    ALTER TABLE MyTable
    ALTER COLUMN PrimaryKeyID BigInt
    --add primary key
    ALTER TABLE MyTable
    ADD CONSTRAINT PK_MyTable PRIMARY KEY (PrimaryKeyID)
    Reference
    http://forums.asp.net/t/1528279.aspx?Alter+script+to+change+the+Primarykey+Column+datatype
    Regards,
    Charlie Liao
    TechNet Community Support

  • What's instance, ROWID and why we use cursor?

    Dear memebers,
    yesterday i have an interview there i faced the following questions.
    1. what is instance?
    2. what is ROWID?
    3. why we use cursor?
    i can give only the last one.
    i am waiting for your answer.
    thanks
    Regards:
    Muhammad Nadeem
    [email protected]

    HY
    Row Identifiers
    Each row in an Oracle database has a unique row identifier, or rowid, which is used internally by the Oracle database to access the row. A rowid is an 18-digit number that is represented as a base-64 number, and it contains the physical address of a row in an Oracle database. You can view the rowid value for rows in a table by specifying the ROWID column in the select list of a query. The query in the following example retrieves the ROWID and customer_id columns from the customers table:
    SELECT ROWID, customer_id
    FROM customers;
    Oracle instance:
    An Oracle instance is the combination of the background processes and
    memory structures. The instance must be started to access the data in the database. Every
    time an instance is started, a System Global Area (SGA) is allocated and Oracle
    background processes are started. Background processes perform functions on behalf of
    the invoking process. They consolidate functions that would otherwise be handled by
    multiple Oracle programs running for each user. The background processes perform
    input/output (I/O) and monitor other Oracle processes to provide increased parallelism
    for better performance and reliability.
    REGARDS

  • ROWID and IOTs

    Greetings,
    I've got some dynamic SQL that selects based on ROWID. Works OK until the table argument is an IOT.
    ORA-01410: invalid ROWIDI have been made aware that IOTs do not carry valid ROWIDs, however, when a ROWID is selected from an IOT, values that can be handled as VARCHAR2 are returned.
    SQL> select rowid from my_iot_table;
    ROWID
    *BAgA7EYCwgsCwQX+
    *BAgA7EYCwgsCwQ7+
    *BAgA7EYCwgsCwRX+If I handle these ROWIDs as character data, is there any guarantee of uniqueness?
    -Kevin

    In a single transaction, I've got a bit of (recursive) code that traverses a tree of related rows in various tables. At each node, it caches the current rowid and compares it to those of all visited nodes to determine if any cycles exist in the data.
    Rowid seemed to be a convenient test for uniqueness.
    -K

  • Problem with Long and BigDecimal DataType convertion

    HI,
    I have an application which talk to MySQL database with Spring JDBC layer and everything runs like a champ :)
    Now I am converting the same application with the same DAO implementation to communicate with oracle database and I am having some trouble converting DataType from database to my java code.
    For example before with MySQL I would convert any Integer coming from the database to Long datatype and it worked. Now it seems that Int datatype from oracle comes as a BigDecimal type.
    I am thinking about two approaches writing an additional implementation to implement my dao interfaces or if there is some trickery that I can bypass doing that and work around these datatype incompatibility from MYSQL to Oracle.
    I can also put bunch of try and catch statements and if fails with Long try with BigDecimal, but still don't buy it as the best solution.
    Here use also code snippet:
    User u = new User();
                        u.setObjectId((Long) m.get("oid"));//This works with MYSQL backend but not with Oracle so the raw object seem to be coming as BigDecimal datatype
                        u.setLogon((String) m.get("logon"));
                        u.setPassword((String) m.get("password"));
                        u.setName((String) m.get("uname"));
                        u.setCompany(companyDAO.getById((Long) m.get("cOid")));Any help will be appreciated.
    Edited by: kminev on Mar 3, 2010 12:25 PM

    //This is my entity class
    public class User implements Comparable<User>  {
        private Long objectId = 0L;
        private Company company;
        private String logon = "";
        private String password = "";
        private String name = "";
        private boolean hasAdminRights=false;
        private boolean hasMaintenanceRights=false;
    //This is my bean class
    <bean id="userDAO" class=" com.myorg.myapp.dao.jdbc.UserImpl">
            <property name="transactionManager">
                <ref local="transactionManager"/>
            </property>
            <property name="companyDAO">
                <ref local="companyDAO"/>
            </property>
            <property name="companyAccessDAO">
                <ref local="companyAccessDAO"/>
            </property>
        </bean>

  • HS generic and long datatypes in Oracle 8i

    I have a problem importing LONG datatype columns
    from Hyperion Pillar to Oracle (version 8.1.6.0.0) using
    the (Hyperion supplied) ODBC driver and generic HS.
    The error message I get is
    ORA-03001: unimplemented feature
    ORA-02063: preceding line from PILLAR.WORLD
    From the message it seems clear that Oracle cannot
    deal with longs using generic connectivity (at least
    in v. 8.1.6).
    My questions:
    1) Is there a workaround ?
    2) Does this work in 9i ?
    Notes:
    1) The problem is not with the ODBC driver, as I
    can see the long datatype columns using another
    tool which connects to Pillar via ODBC.
    2) HS has been set up correctly because all datatypes
    other than long can be viewed in Oracle without any
    problems.
    3) Operating System: Windows NT 4.00.1381
    Any help would be much appreciated!
    Kailash.

    Thanks for the reply.
    Pillar LONGS (or MEMO, as they are referred to in Pillar)
    map to ODBC SQL_LONGVARCHAR. So it appears that the
    mapping is OK, and that SELECTing from these columns
    should be possible via generic connectivity.
    Any other ideas on what may be wrong? Any help is
    much appreciated.
    Thanks,
    Kailash.

  • CLOB and LONG datatypes

    I have a problem with needing to display fields in a report that are stored in the database as CLOB.
    The report isn't too complicated, and can be put together using folders in Admin.
    There is a table in the database that stores text from reports. Each report is identified by its case id, and then there may be a number of reports for each case (let's say 1-5 for the purposes of this explaination). There will then be three sections of text in each report, identifed in the database by section numbers.
    The fields needed are the case number (case_id), the report number (report_no), the section number (sect_no) and the section text (sect_text)
    All of the fields are numeric, except sect_text, which is a CLOB datatype.
    There are two queries, one to select the case id, min report number and first section of text and the other to select the case id, max report number and last section of text. The aim being a report that shows the start of the first report and the end of the last one.
    So, that's the background. All of the queries to select the data work fine in sqlplus. However they can't be displayed in Disco because it brings in CLOB fields as LONG, and can't group them (which it has to do for the MAX and MIN)
    I'd rather not set the whole thing up as a view on the DB, as I'd prefer to have the flexibiility of editing it in discoverer
    Any tips?

    Hi
    I do have a tip. Please take a look at this thread that I was involved in a couple of years ago:
    CLOB show up as item
    And here is another one that might help:
    Possible for Discoverer to display BLOB type documents stored in database?
    Best wishes
    Michael

Maybe you are looking for

  • Open/Save Dialog Box SLOW

    My Mac has slowed down to an absolute crawl. I have reinstalled the OS, run Disk Warrior, Disk Utility, removed my preferences folder to see if something in there was actin' up, I've repaired the permissions, etc... Yet in any application (whether it

  • My computer is asking for a 6 digits code to unlock the system after updating it. How do I fix it??

    I updated my mac with the usual update, and then suddenly my mac shut down. After trying to turn it on everything was fine except for the fact that I am not able to use it because I can't log on to desktop- my MacBook is asking me for a 6 digit code

  • Detecting which line the User is Editing IN table control

    Hi, I am doing a Dialog programming where there is a Table control. Now the problem is I have to decide to checks  certain rules based on data entered in the Table control. But the Rules should be applicable only to the Row in which the User is enter

  • IPhone4 not showing up in My Computer?

    I couldn't locate my iPhone4's storage for simple manual picture purposes on my desktop computer's ''My Computer'' page but I can locate it on my laptop's, weird. Anyway to fix this?

  • HP 7700 Desktop Power on no green light nor monitor display

    Hi. I have a HP 7700 which was been working fine for months, however now unable to use. Power up and red blinking light appears, but doesn't change to green. Monitor display is same as when monitor on but of switched off. Can hear fans whirling and a