Call Logical database KDF
Hi expert.
now that, I'm using Logical database KDF for report module AP, but i meet issue following.
first way i used SE38 and choose radio Attribute and Input LDB is KDF.
In program I get only NODE BSIK but structure BSEGA Not is initial( I don't get BSEG anywhere)
second way. I used FM LDB_PROCESS to call LDB KDF.
I also get NODE BSIK then BSEGA Is initial.
Please anybody to me first way structure BSEGA have data, second way it haven't data.
Thank & best regards,
Dungnv
don't use fm but include KDF as in standard report RFKOPO00
hope that helps
Andreas
Similar Messages
-
ABAP query using logical database KDF is not populating custom fields
Hi Experts ,
I created two following queries
1. VENDORCATKDF – uses KDF logical database
2. VENDORCATLFA1 – uses table = LFA1
I’m pulling the same information in both queries:
· Vendor Number
· Country
· Vendor Name
· Vendor Category (custom fields added to LFA1)
The results for the query that uses the logical database KDF is incorrect. It doesn’t pull in the flag on the custom field LFA1-ZMRO. Even though the logical database KDF is made up of the table LFA1 and has these fields.
Is there something that can be done – so that all of these “custom” category fields under LFA1 (such as LFA1-ZZMRO) – get pulled into queries – when we use the logical database KDF ?Hi,
I have got the error removed by ensuring that fields from one table are a part of one line ( taking help of ruler) only. But the underlying problem remains, the output is not ALV but List output.
I do not think having additional fields in the query is reason for this.
Is it bcoz iI am adjusting the output length of columns to ensure no hierarchical error ?
Can we not have a query using LDB which is shown as SAP List?
Regards,
Garima. -
Hello,
i want to select all open items of the vendor accounts.
I have tried this with the logical database KDF and the selection screen 900 for open items.
Now i have the problem, that i also want the customer items of the vendor account.
Can i get this items, too, with the logical database KDF or have i to select this separately?
Thanks.
NicoleNicole.
You can select customer / vendor open items directly from tables.
BSID : Customer Open Items
BSIK : Vendor Open Items
Regards,
Mahesh -
Multiple calling logical database ADA
Hello,
I need to call logical database ADA two times in my program. I use calling logical database using LDB_PROCESS function module. I need to call LDB for depreciation areas 01 and 60. If I call second time, I get exception LDB_NOT_REENTRANT. I found, that for multiple calls of LDB, there should be LDB_PROCESS_INIT subroutine in logical database proram. In this case, program is SAPDBADA and in this program, LDB_PROCESS_INIT is missing.
Could you pls. help me, how to call ADA logical database two times?
Thanks®ards,
JirkaThe exception LDB_NOT_REENTRANT means: The logical database is not prepared to accept several successive calls within a transaction. So obviously you can't use LDB_PROCESS for your purpose.
Perhaps your goal is possible if you use a sequence of commands
GET <ldb_node_1>.
GET <ldb_node_1> LATE.
GET <ldb_node_2>.
GET <ldb_node_2> LATE.
etc...
where ldb_node_1, ldb_node_2, etc... are some nodes included in logical database ADA. As I am not familiar with this particular LDB I can't tell which nodes are required to achieve your goal. -
Logical Database KDF ( FBL1N )
Hi SPecialist
I am trying to add a new field in the logical database KDF. I have several tables here and I would like to add the field USERNAME from BKPF
I suppose that it is possible because I can see the following tables
LFA1 Vendor Master (General Sectio
ADDR1_VAL Address Data
LFAS Vendor Master (General Part E
LFBK Vendor Master (Bank Details)
LFB1 Vendor Master (Company Code)
LFB5 Vendor Master (Dunning Data)
LFC1 Vendor Master (Transaction Fig
LFC3 Vendor Master (Transaction Fig
BSIK Accounting: Secondary Index fo
ADMI_FILES Archive Files
BSIKEXT Secondary Index & Additions Se
BKPF Accounting Document Header
But when I try to add the field in the functional groups It doesnt appear in the transaction FBL1N.
Any idea??
ThanksHi:
Have you tries adding this USERNAME field to FBL1N report using menu...settings...special fields..I think this can be done via special fields addition...Please note that in special fields , fields from BKPF and BSEG can be added. For adding other fields like Vendor name e.t.c you will have to make use of BTE 1650 in FIBF...Please take help for ABABPER. Hope it helps.
Regards -
Duplicated entries in BSIK using Logical Database KDF
Hello everyone,
I'm using Logical Database KDF to retrieve some data, but i'm getting duplicated entries when getting to BSIK. Can anyone point out in my program what could i be doing wrong?
If i put a breakpoint in the line immediatly below GET bsik, i can watch several entries being duplicated.
Thanks in advance to everyone,
Nuno
START-OF-SELECTION.
GET lfa1.
MOVE-CORRESPONDING lfa1 TO t_alv.
GET lfb1.
GET bsik.
MOVE-CORRESPONDING bsik TO t_alv.
CLEAR bkpf.
SELECT SINGLE * FROM bkpf CLIENT SPECIFIED
WHERE mandt = syst-mandt
AND bukrs = bsik-bukrs
AND belnr = bsik-belnr
AND gjahr = bsik-gjahr.
t_alv-xblnr = bkpf-xblnr.
SELECT * FROM bset CLIENT SPECIFIED
WHERE mandt = syst-mandt
AND bukrs = bsik-bukrs
AND belnr = bsik-belnr
AND gjahr = bsik-gjahr.
t_alv-mwskz = bset-mwskz.
t_alv-hwbas = bset-hwbas.
t_alv-hwste = bset-hwste.
t_alv-dmbtr = bset-hwbas + bset-hwste.
t_alv-stceg = lfa1-stceg.
APPEND t_alv.
ENDSELECT.Hello Nuno Centeio ,
According to the table definition there can be more than one entries for a vendor based on the table key definition.
Thanks,
Greetson -
hi friends,
plz explain me how to call logical database in a report program?hi,
Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables by linking them to executable ABAP programs.
However, from Release 4.5A, it has also been possible to call logical databases using the function module LDB_PROCESS. This allows you to call several logical databases from any ABAP program, nested in any way. It is also possible to call a logical database more than once in a program, if it has been programmed to allow this. This is particularly useful for programs with type 1.
Logical databases contain Open SQL statements that read data from the database. You do not therefore need to use SQL in your own programs. The logical database reads the program, stores them in the program if necessary, and then passes them line by line to the application program or the function module LDB_PROCESS using an interface work area.
Logical Databases - Views of Data
A logical database provides a particular view of database tables in the R/3 System. It is always worth using logical databases if the structure of the data that you want to read corresponds to a view available through a logical database.
The data structure in a logical database is hierarchical. Many tables in the R/3 System are linked to each other using foreign key relationships. Some of these dependencies form tree-like hierarchical structures. Logical databases read data from database tables that are part of these structures.
Advantages of Logical database -
1) No need of programming for retrieval , meaning for data selection
2) Easy to use standard user interface, have check completeness of user input.
Disadvantages
1) Fast in case of lesser no. of tables But if the table is in the lowest level of hierarchy, all upper level tables should be read so performance is slower.
GO THROUGH THE LINKS
http://www.sap-basis-abap.com/saptab.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9bfa35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c6/8a15381b80436ce10000009b38f8cf/frameset.htm
/people/srivijaya.gutala/blog/2007/03/05/why-not-logical-databases
Re: **LDB**
www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_Logical_Database_FAQ.html
www.sap-img.com/abap/abap-interview-question.htm
www.sap-img.com/abap/quick-note-on-design-of-secondary-database-indexes-and-logical-databases.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db9bb935c111d1829f0000e829fbfe/content.htm
Use Tcode SE36 For creating Logical Database.
Here is a simple Program on Logical database.
NODES: spfli,sflight.
START-OF-SELECTION.
WRITE 'Test Program for GET'.
*Fetching SPFLI table
GET spfli.
WRITE: / 'Carrid:', spfli-carrid,
'Connid:', spfli-connid.
*Fetching SFLIGHT table
GET sflight.
SKIP 5.
WRITE: / 'Carrid:', sflight-carrid,
'Connid:', sflight-connid.
logical database
logical database
http://help.sap.com/saphelp_nw04/helpdata/en/60/183d78163011d2953c0000e8353423/frameset.htm
general
example program
http://help.sap.com/saphelp_nw04s/helpdata/en/9f/db9be035c111d1829f0000e829fbfe/frameset.htm
regards,
pavan
REWARD POINTS IF USEFUL -
Hi,
I have created one logical database using BSAK & BSEG named as "ZVENLDB".
While iam calling this LDB into abap program...it is showing error that "BSAK is not a node of the logical database".
Could any one tell me where might be the problem?
...this is abap program...
report Z_SAMPLE.
NODES: BSAK,BSEG.
GET BSAK.
SKIP.
WRITE:/BSAK.
GET BSEG.
SKIP.
WRITE:/BSEG.
Reward guaranteed...
KakiHere is the link for help for more details:
http://help.sap.com/saphelp_47x200/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm
Hope this will be helpful. -
Exclude one field from Logical Database's dynamic selection screen
Hi Guru,
I have a requirement to amend a program to exclude the document number field (bsik-belnr) from the dynamic selection-screen of the logical database KDF(Vendor Database) so that the program will not filter according to the document number.
I have use the below syntax in my zprogram.
selection-screen exclude select-options: doc-no.
However I get syntax error "The addition EXCLUDE is only allowed in INCLUDE DBKDFSEL".
Please advice.
Best Regards,
FungThe selection part of the logical database defines input fields for selecting data.
The runtime environment displays these on the selection screen when you run an executable program linked to the logical database.
Include called DB<ldbname>SEL.
SELECTION-SCREEN BEGIN OF VERSION ver TEXT-xxx.
SELECTION-SCREEN EXCLUDE ... .
SELECTION-SCREEN END OF VERSION ver.
Defines a selection screen version (with a three-character name ver ). Between BEGIN OF VERSION and END OF VERSION , you can exclude selection screen objects for the version ver , i.e. remove them from the selection screen with SELECTION-SCREEN EXCLUDE.
SELECTION-SCREEN DYNAMIC SELECTIONS FOR TABLE dbtab
If one of these tables is active in the report (i.e. it is declared under TABLES or lies somewhere on the path from the root of the database hierarchy to a table declared with TABLES ), a pushbutton called 'Dynamic selections' appears on the selection screen. -
Hi All, I am quite familiar with Logical Databases but I need to understand the following.
1) I am using LDB ADA, but I want to use my own Selection Screen and not the default one that the LDB provides. I know I must put something in AT SELECTION-SCREEN but am unsure what.
2) Once I get the data, I want to store the data in an internal table - how do I go about doing this? If you can provide a code example that would be great.
Points for any relevant help.Hi,
A logical database is a special ABAP/4 program which combines the contents of certain database tables. You can link a logical database to an ABAP/4 report program as an attribute. The logical database then supplies the report program with a set of hierarchically structured table lines which can be taken from different database tables.
Logical database structures
There are three defining entities in an SAP logical database. You must be clear on all three in order to create and use one.
Table structure: Your logical database includes data from specified tables in SAP. There is a hierarchy among these tables defined by their foreign keys (all known to SAP), and you are going to define a customized relationship between select tables. This structure is unique and must be defined and saved.
Data selection: You may not want or need every item in the referenced tables that contributes to your customized database. There is a selection screen that permits you to pick and choose.
Database access programming: Once youve defined your logical database, SAP will generate the access subroutines needed to pull the data in the way you want it pulled.
Creating your own logical database
Heres a step-by-step guide:
1) Call up transaction SLDB (or transaction SE36). The path you want is Tools | ABAP Workbench | Development | Programming Environment | Logical Databases. This screen is called Logical Database Builder.
2) Enter an appropriate name in the logical database name field. You have three options on this screen: Create, Display, and Change. Choose Create.
3) Youll be prompted for a short text description of your new logical database. Enter one. Youll then be prompted to specify a development class.
4) Specify a root node, or a parent table, as the basis of your logical database structure. You can now place subsequent tables under the root table as needed to assemble the data object you want. You can access this tree from this point forward, to add additional tables, by selecting that root node and following the path Edit | Node | Create. Once youve saved the structure you define in this step, the system will generate the programming necessary to access your logical database. The best part is you dont have to write a single line of code.
Noted point is we cant add any selection criteria thru our se38 program if you are attaching any LDB to program.Ist of no use.
If you want to change selection criteria to the existing LDB, you have to goto SE36 tcode and provide LDB name and choose "Change" mode by selecting "Selections" Radio button.
declaration of params is different compared to normal se38 program in some aspects.
PARAMETERS :p_curr LIKE bkpf-waers FOR TABLE bkpf OBLIGATORY.
this BKPF table should be one of the node in the "Structure" Radio button.
Thanks
Sivaparvathi
Please reward points if helpful. -
Steps to create LOGICAL DATABASE in sap
hi guys,
i have gone through many documents about LDB. But, i didnt get the steps to create a LDB.
plz provide me with the steps to be followed to create a LDB.
thnx,
shivaa.Hi Shiva,
This might help you!
Logical database structures
There are three defining entities in an SAP logical database. You must be clear on all three in order to create and use one.
Table structure: Your logical database includes data from specified tables in SAP. There is a hierarchy among these tables defined by their foreign keys (all known to SAP), and you are going to define a customized relationship between select tables. This structure is unique and must be defined and saved.
Data selection: You may not want or need every item in the referenced tables that contributes to your customized database. There is a selection screen that permits you to pick and choose.
Database access programming: Once youu2019ve defined your logical database, SAP will generate the access subroutines needed to pull the data in the way you want it pulled.
Creating your own logical database
ABAP/4 (Advanced Business Application Programming language, version 4) is the language created by SAP for implementation and customization of its R/3 system. ABAP/4 comes loaded with many predefined logical databases that can construct and table just about any conventional business objects you might need in any canned SAP application. However, you can also create your own logical databases to construct any custom objects you care to define, as your application requires in ABAP/4. Hereu2019s a step-by-step guide:
1. Call up transaction SLDB (or transaction SE36). The path you want is Tools | ABAP Workbench | Development | Programming Environment | Logical Databases. This screen is called Logical Database Builder.
2. Enter an appropriate name in the logical database name field. You have three options on this screen: Create, Display, and Change. Choose Create.
3. Youu2019ll be prompted for a short text description of your new logical database. Enter one. Youu2019ll then be prompted to specify a development class.
4. Now comes the fun part! You must specify a root node, or a parent table, as the basis of your logical database structure. You can now place subsequent tables under the root table as needed to assemble the data object you want. You can access this tree from this point forward, to add additional tables, by selecting that root node and following the path Edit | Node | Create. Once youu2019ve saved the structure you define in this step, the system will generate the programming necessary to access your logical database. The best part is you donu2019t have to write a single line of code.
Watch out!
The use of very large tables will degrade the performance of a logical database, so be aware of that trade-off. Remember that some tables in SAP are very complex, so they will be problematic in any user-defined logical database.
Declaring a logical database
Hereu2019s another surprising feature of logical databases: You do not assign them in your ABAP/4 Code. Instead, the system requires that you specify logical databases as attributes. So when you are creating a report, have your logical database identifier (the name you gave it) on hand when you are defining its attributes on the Program Attributes screen. The Attributes section of the screen (the lower half) will include a Logical database field, where you can declare your logical database.
Logical databases for increasing efficiency
Why else would you want to create a logical database? Consider that the logical databases already available to you begin with a root node and proceed downward from there. If the data object you wish to construct consists of items that are all below the root node, you can use an existing logical database program to extract the data, then trim away what you donu2019t want using SELECT statementsu2014or you can increase the speed of the logical database program considerably by redefining the logical database for your object and starting with a table down in the chain. Either way, youu2019ll eliminate a great deal of overhead.
Reward if useful.
Thankyou,
Regards. -
Regarding Logical database and select statement..
Hi
Experts.
i would like to know the diff b/w logical data base & select statement while using report.
wt is the use of logical databases in R/3. is there any advantage used in the reports.
Thanks & Regards..
Spandana.Dear Spandana,
Go through the below description of LDB. I hope you wil get a fair amount of idea.
SAP comes loaded with all the extras. Among the extras that are most helpful to IT managers are all the access routines needed to pull any business object that managers can think of out of SAP databases. However, SAP has not thought of everything where your particular applications are concerned. SAP organizes its standard database tables to service business units based on conventional business applications. Itu2019s likely your business requires something new, perhaps even something exotic. In that case, you will need to create a new database, using information from different places. Basically, you need a logical database. You need to create a virtual business data object repository consisting of a new kind of record or table that suits your purposes. In addition, the repository should be composed of information that is actually stored in a number of different locations, none of them necessarily logically associated with one another. Letu2019s take a closer look at creating logical databases.
A case for a logical database
Suppose my company manufactures widgets of the most obscure variety, and they are components of other widgets. I sell my widgets as raw material for the more sophisticated widgets built by others, but in some cases I actually partner with other manufacturers in creating yet another class of widget. Now, in my world, I consequently have customers who are also partners. I sell to them and I partner with them in manufacturing and distribution. Also, I need an application that uses both of these dual-use relationships.
Essentially, I have a customer database and a partner database. Neither contains records that are structured to contain the identifying particulars of the other. Thus, I need a hybrid database that gives me tables detailing these hybrid relationships. What can I do? I can go the long way around and write a new database, pulling information from both and creating new objects with a customized program that I write by hand. However, this process is cumbersome and contains maintenance issues. On the other hand, I can use SAPu2019s logical database facility, create my logical database in a couple of minutes, and have no maintenance issues at all.
Logical database structures
There are three defining entities in an SAP logical database. You must be clear on all three in order to create and use one.
u2022 Table structure: Your logical database includes data from specified tables in SAP. There is a hierarchy among these tables defined by their foreign keys (all known to SAP), and you are going to define a customized relationship between select tables. This structure is unique and must be defined and saved.
u2022 Data selection: You may not want or need every item in the referenced tables that contributes to your customized database. There is a selection screen that permits you to pick and choose.
u2022 Database access programming: Once youu2019ve defined your logical database, SAP will generate the access subroutines needed to pull the data in the way you want it pulled.
Creating your own logical database
ABAP/4 (Advanced Business Application Programming language, version 4) is the language created by SAP for implementation and customization of its R/3 system. ABAP/4 comes loaded with many predefined logical databases that can construct and table just about any conventional business objects you might need in any canned SAP application. However, you can also create your own logical databases to construct any custom objects you care to define, as your application requires in ABAP/4. Hereu2019s a step-by-step guide:
1. Call up transaction SLDB (or transaction SE36). The path you want is Tools | ABAP Workbench | Development | Programming Environment | Logical Databases. This screen is called Logical Database Builder.
2. Enter an appropriate name in the logical database name field. You have three options on this screen: Create, Display, and Change. Choose Create.
3. Youu2019ll be prompted for a short text description of your new logical database. Enter one. Youu2019ll then be prompted to specify a development class.
4. Now comes the fun part! You must specify a root node, or a parent table, as the basis of your logical database structure. You can now place subsequent tables under the root table as needed to assemble the data object you want. You can access this tree from this point forward, to add additional tables, by selecting that root node and following the path Edit | Node | Create. Once youu2019ve saved the structure you define in this step, the system will generate the programming necessary to access your logical database. The best part is you donu2019t have to write a single line of code.
Watch out!
The use of very large tables will degrade the performance of a logical database, so be aware of that trade-off. Remember that some tables in SAP are very complex, so they will be problematic in any user-defined logical database.
Declaring a logical database
Hereu2019s another surprising feature of logical databases: You do not assign them in your ABAP/4 Code. Instead, the system requires that you specify logical databases as attributes. So when you are creating a report, have your logical database identifier (the name you gave it) on hand when you are defining its attributes on the Program Attributes screen. The Attributes section of the screen (the lower half) will include a Logical database field, where you can declare your logical database.
Logical databases for increasing efficiency
Why else would you want to create a logical database? Consider that the logical databases already available to you begin with a root node and proceed downward from there. If the data object you wish to construct consists of items that are all below the root node, you can use an existing logical database program to extract the data, then trim away what you donu2019t want using SELECT statementsu2014or you can increase the speed of the logical database program considerably by redefining the logical database for your object and starting with a table down in the chain. Either way, youu2019ll eliminate a great deal of overhead.
Regards
Arindam -
Modifying Dynamic selection in standard logical database
Hello guys,
I have a requirement to add a field to a dymamic selection of standard programs.
The standard programs used the logical database KDF.
I have created a custom selection view and included the required field which is from table BKPF.
But this field is not appearing as the table BKPF is not defined as a node in Dynamic selection but in only field selection.
Can anyone please provide me with come help on this?
I need to add the a field from BKPF to the dynamic selection of standard logical DB KDF. Is this possible?
Thanks and regardsHello Thomas,
thank you very much for the precious help.
I appended the field BKTXT to BSIK and BSAK as used in logical database and these are automatically filled for new postings thanks to Move corresponding (as indicated).
We are left with only to feed these new fields with existing data/records.
kind regards..
Edited by: Devi on May 19, 2009 12:51 PM
Edited by: Devi on May 19, 2009 12:51 PM -
Hi,
Is it common to use logical database for HR report?? How about other module such as SD/MM??
Regards,
KitHi,
Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables by linking them to executable ABAP programs.
However, from Release 4.5A, it has also been possible to call logical databases using the function module LDB_PROCESS. This allows you to call several logical databases from any ABAP program, nested in any way. It is also possible to call a logical database more than once in a program, if it has been programmed to allow this. This is particularly useful for programs with type 1.
Logical databases contain Open SQL statements that read data from the database. You do not therefore need to use SQL in your own programs. The logical database reads the program, stores them in the program if necessary, and then passes them line by line to the application program or the function module LDB_PROCESS using an interface work area.
Logical Databases - Views of Data
A logical database provides a particular view of database tables in the R/3 System. It is always worth using logical databases if the structure of the data that you want to read corresponds to a view available through a logical database.
The data structure in a logical database is hierarchical. Many tables in the R/3 System are linked to each other using foreign key relationships. Some of these dependencies form tree-like hierarchical structures. Logical databases read data from database tables that are part of these structures.
The diagram illustrates how the R/3 System might represent the structure of a company. A logical database can read the lines of these tables one after the other into an executable program in a sequence which is normally defined by the hierarchical structure. The term logical database is sometimes used to mean not only the program itself, but also the data that it can procure.
Tasks of Logical Databases
As well as allowing you to read data from the database, logical databases also allow you to program other tasks centrally, making your application programs less complicated. They can be used for the following tasks:
Reading the same data for several programs.
The individual programs do not then need to know the exact structure of the relevant database tables (and especially not their foreign key relationships). Instead, they can rely on the logical database to read the database entries in the right order during the GET event.
Defining the same user interface for several programs.
Logical databases have a built-in selection screen. Therefore, all of the programs that use the logical database have the same user interface.
Central authorization checks
Authorization checks for central and sensitive data can be programmed centrally in the database to prevent them from being bypassed by simple application programs.
Improving performance
If you want to improve response times, logical databases permit you to take a number of measures to achieve this (for example, using joins instead of nested SELECT statements). These become immediately effective in all of the application programs concerned and save you from having to modify their source code
Reward Points if useful
Raghunath.S
9986076729 -
How to know logical database supports Dynamic Selections
hi all,
1. Logical database KDF supports Dynamic Selections
2. How to know logical database 'KDF' supports Dynamic SelectionsYou might find an answer regarding dynamic 'WHERE' statements in standard SAP report SAPDBKDF
Maybe you are looking for
-
Why won't it let me download apps?
I just got my iphone 5s last night, and I proceeded to download all the apps I wanted until I came across one that said I needed to update, so I updated my phone and in the morning I downloaded that app and one more, after which when I tried to downl
-
Different creation dates on different computers
I downloaded the same photos from the same camera on the same day to my home and office computers, both into iPhoto. At home, the creation date is correct, but at work the date is wrong in every way including the year. I checked the system time and d
-
TS1292 My iTunes card I entered is not showing up on my balance
Please help me with my I tunes account my new balance is not showing
-
Issue with lost messages after updating....
I was wondering if anyone could shed some light on the following.... I recently (...regretfully) completed the software update to v 20.0.019 via PC suite...before the update I made a back up of ALL files onto my SD card, which according to my backup
-
Why do my photos in "photos" look so washed out compared to iPhoto?
I don't like "PHOTOS," and I don't know why Apple came out with it for OS10. My pictures look washed out compared to how they look in iPhoto I can't just click on a photo and see it in full screen. What am I missing?