Tracking theives, does the 3g model's gps tracking justify the added cost?

I'd like to track down my ipad if it ever gets stolen. Ive read mixed reports on the effectiveness of the skyhook wifi-only model vs the skyhook + 3g/GPS model, and whether i would need to buy a plan just to use the gps on it. Anyone have experience with this?

David M Brewer wrote:
iPadKisser wrote:
Just call 911.
Call 911 for a missing iPad! Are you crazy And let's say you find the iPad? What are the police going to do? Probably nothing...
In some localities you can get charged for tying up the 911 line for a non-emergency.

Similar Messages

Apple new macbook pro dosent have a disk drive. Does the older model have a problem with the disc drive and so is removed in the new model?

apple new macbook pro dosent have a disk drive. Does the older model have a problem with the disc drive and so is removed in the new model?

No. Apple replaced the disk drive with a solid state drive (SSD) instead. The SSD is faster the old disk drive.
Allan

I was wondering how I pick the right model for my s10 on the lenovo site/

Hi all
I have an S10 model number 4231 but when I go to the lenovo driver page AFTER I select 4231 it asked for a futher sub model like 2AU or 32U
my problem is that I don't know where to find this about my computer. I checked the system screen and this is all there is
model 4231
s/n ********
mo: r3py38911906
factory id S
ideapad S10
the bios is lenovo 14cn34ww 08/20/2008
the seriel is FN1083625eodnnn
any help would be excellent.
Moderator note: serial number removed for member's protection.
Solved!
Go to Solution.

hey bdesigns
certainly not under warranty are they ever :-)
everything backed up to google drive so all good there :-)
real bummer is that I can't get into the bios despite the fact that ALL passwords are clear on this S10 I get the message
"All items on this menu cannot be modified in user mode.
If any items require changes, please consult your system supervisor"
There is no hard drive detected and I'm pretty sure that it's ok. It's a WD5000bpvt and "was" working like a champ. Ho hum ce la vie I long for the days when I used Tandem computers and dos. Life seemed to be so understandable then...
have a great evening
Mk

My dad has an imac G5 from 2005, and I'm wondering if we can bring it to the Apple store and replace it with one of the newer models. How much would the G5 be worth and how much money would we have to put on top of it to buy the newer model?

How much is the G5 worth? The one from 2005.

The Apple Store will offer to recycle it for free, you are better off selling it on ebay or elsewhere, I have seen decent looking ones go from $80-$250 here in Australia.
You are looking at $1000 + to get a new one

GPS Tracking program that continues to track while using other iPhone apps

Does anyone know of a GPS tracking app for the iPhone 3G that will continue to track while listening to music or answering calls? The few apps I've tried quit logging when you change to another app.

Thanks - hopefully Apple will address this soon. I'm not willing to hack/jailbreak my phone just to get this functionality.
One last dig:
This is the unfortunate reason that I've stayed away from Apple for so long. They make WOW stuff that is pretty and neat to use as long as you stay inside the "box" so to speak. I guess I'll have to take my old blackberry running with me - it can play music AND track your run with GPS. Who would want to do that?

Do I need 3G on iPad2 for GPS tracking?

I want to use iPad 2 as a GPS router. I think this could only be done with 3G with the iPad1. I believe this is not the case with the iPad2 (?). From what I understand, the 3G is now stricktly for internet connection through cel phone network. Am I correct?
Tks

3G has nothing directly to do with GPS. It's just that the 3G model is the only one of to two to also have GPS hardware; the WiFi-only model does not. So if you want true GPS capability, you must have the 3G model of iPad (this is the same for the iPad 1 as well as the iPad 2).
Regards.

Paradigm Shift: the WDP Model & the Power to Bind

As a developer coming from an OO/java background, I recently started to study and use the Java Web Dynpro framework for creating enterprise portal applications.
Up to this point, I've developped 2 or 3 WDP projects - and in so doing, I've tried to reconciliate my java-influenced development methods with the SAP way of doing things. I'd say for the most part it was rather painless. I did, however, find a serious problem as far as I'm concerned in the way SAP has promoted the use of the java bean model importer.
<a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/251697223">david Beisert</a> created this tool and presented it to the SDN community in 2004 in his <a href="/people/david.beisert/blog/2004/10/26/webdynpro-importing-java-classes-as-model The same year (don't know if it was before or after), SAP published '<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c">Using EJBs in Web Dynpro Applications</a>'. Both of these works presented simplified examples of invoking remote functions on EJB backends (an add() function in the case of David Beisert's example, and a calculateBonus() function in the case of the SAP publication). Accordingly, they both recommended the use of the Command Bean pattern as an implementation strategy for their respective examples. Which I don't totally disagree with, in these particular circumstances. A simple execute() method is perfectly suitable if one needs to EXECUTE a remote function call - whether it be a calculate() method invoked on a EJB Session Bean or an RFC call made to some remote ABAP system.
Problem is, not everything in life is a function call ! To me, it makes very little sense to model everything as a command if it doesn't match your business model. The needs of your application should dictate the architecture of your model and not the other way around.
This unjustifiable fixation on the Command Bean pattern is probably to blame for the fact that very little up to this point seems to have been written on the subject of the power of the binding mecanism as a most powerful tool in the arsenal of the Web Dynpro developer.
What's this ?
Binding can make it possible to abstract away most of the nitty gritty context node navigation and manipulation logic and replace it with more intuitive and more developer-friendly model manipulation logic.
There was a time when programs that needed persistence were peppered with database calls and resultset manipulation logic. Hardly anyone codes like that anymore.. and with good reason. The abstraction power of Object Oriented technologies have made it possible to devise human friendly models that make it possible for developers to concentrate on business logic, and not have to waste time dealing with the low-level idiosyncrasies of database programming. Whether it be EJBs, JDO, Hibernate... whatever the flavour... most serious projects today utilize some sort of persistence framework and have little place for hand-coding database access logic.
I feel that the WD javabean model offers the same kind of abstraction possibilities to the Web Dynpro developer. If you see to it that your WD Context and javabean model(s) mirror each other adequately, the power of binding will make it possible for you to implement most of your processing directly on the model - while behind the scenes, your context and UI Elements stay magically synchronized with your user's actions:
+-------------+        +-------------------+         +--------------+        +------------+
|    Model    |<-bound-| Component Context |<-mapped-| View Context |<-bound-| UI Element |
+-------------+        +-------------------+         +--------------+        +------------+
                       o Context Root                o Context Root
                       |                             |
ShoppingCartBean <---- +-o ShoppingCart Node <------ +-o ShoppingCart Node
{                        |                             |
Collection items <---- +-o CartItems Node <--------- +-o CartItems Node <-- ItemsTable
{                        |                             |
    String code; <-------- +- Code <-------------------- +- Code <----------- CodeTextView
    String descrip; <----- +- Description <------------- +- Description <---- DescTextView
Let's examine an example of this concept. I propose a simple but illustrative example consisting of a shopping cart application that presents the user with a collection of catalog items, and a shopping cart in which catalog items may arbitrarily be added and/or removed.
The Component and View contexts will be structured as follows:
   o Context Root
   |
   +--o ProductCatalog       (cardinality=1..1, singleton=true)
   | |
   | +--o CatalogItems      (cardinality=0..n, singleton=true)
   |     |
   |     +-- Code
   |     +-- Description
   |
   +--o ShoppingCart         (cardinality=1..1, singleton=true)
      |
      +--o ShoppingCartItems (cardinality=0..n, singleton=true)
         |
         +-- Code
         +-- Description
Let's examine how a conventional Command Bean implementation of this component could be coded. Later on, I'll present a more object-oriented model-based approach. We can then compare the differences.
public class ProductCatalogCommandBean
   // collection of catalog items
   Collection items = new ArrayList();
   public void execute_getItems()
      // initialize catalog items collection
      items = new ProductCatalogBusinessDelegate().getItems();
This command bean will serve as a model to which the ProductCatalog node will be bound. This happens in the supply function for that node in the component controller:
public supplyProductCatalog(IProductCatalogNode node, ...)
   // create model
   model = new ProductCatalogCommandBean();
   // load items collection
   model.execute_getItems();
   // bind node to model
   node.bind(model);
No supply function is needed for the ShoppingCart node, since it is empty in its initial state. Its contents will only change based on the user adding to or removing items from the cart. These operations are implemented by the following two event handlers in the view controller:
public void onActionAddItemsToCart()
   // loop through catalog items
   for (int i = 0; i < wdContext.nodeCatalogItems().size(); i++)
      // current catalog item selected ?
      if (wdContext.nodeCatalogItems().isMultiSelected(i))
         // get current selected catalog item
         ICatalogItemsElement catalogItem = wdContext.nodeCatalogItems().getElementAt(i);
         // create new element for ShoppingCartItem node
         IShoppingCartItemsElement cartItem = wdContext.createShoppingCartItemsElement();
         // initialize cart item with catalog item
         cartItem.setCode       (catalogItem.getCode());
         cartItem.setDescription(catalogItem.getDescription());
         // add item to shopping cart
         wdContext.nodeShoppingCartItems().addElement(cartItem);
public void onActionRemoveItemsFromCart()
   // loop through cart items
   for (int i = 0; i < wdContext.nodeShoppingCartItems().size();)
      // current shopping cart item selected ?
      if (wdContext.nodeShoppingCartItems().isMultiSelected(i))
         // get current selected item
         IShoppingCartItemsElement item = wdContext.nodeShoppingCartItems().getElementAt(i);
         // remove item from collection
         wdContext.nodeShoppingCartItems().removeElement(item);
      else
         // process next element
         i++;
From what I understand, I believe this is the typical way SAP recommends using Command Beans as a model in order to implement this type of simple component.
Let's see how the two same event handlers could be written with a more comprehensive object model at its disposal. One whose role is not limited to data access, but also capable of adequately presenting and manipulating the data that it encapsulates. (The actual code for these model beans will follow)
// I like to declare shortcut aliases for convenience...
private ProductCatalogBean catalog;
private ShoppingCartBean   cart;
// and initialize them in the wdDoInit() method...
public wdDoInit(...)
   if (firstTime)
      catalog = wdContext.currentNodeProductCatalog().modelObject();
      cart    = wdContext.currentNodeShoppingCart ().modelObject();
Now the code for the event handlers:
public void onActionAddItemsToCart()
   // add selected catalog items to shopping cart items collection
   cart.addItems(catalog.getSelectedItems());
public void onActionRemoveItemsFromCart()
   // remove selected shopping cart items from their collection
   cart.removeItems(cart.getSelectedItems());
I feel these two lines of code are cleaner and easier to maintain than the two previous context-manipulation-ridden versions that accompany the command bean version.
Here's where the models are bound to their respective context nodes, in the Component Controller.
public supplyProductCatalogNode(IProductCatalogNode node, ...)
   node.bind(new ProductCatalogBean(wdContext.getContext()));
public supplyShoppingCartNode(IShoppingCartNode node, ...)
   node.bind(new ShoppingCartBean(wdContext.getContext()));
Notice that a context is provided in the constructors of both models (a generic context of type IWDContext). We saw earlier that our model needs to be able to respond to such requests as: catalog.getSelectedItem(). The user doesn't interact directly with the model, but with the Web Dynpro UI Elements. They in turn update the context... which is where our model will fetch the information it requires to do its job.
Also note that a model is provided for the shopping cart here, even though it has no need to access or execute anything on the back-end. Again, the model here is not being used as a command bean, but rather as a classic object model. We simply take advantage of the power of binding to make ourselves a clean and simple little helper that will update for us all the relevant context structures behind the scenes when we tell it to.
Here are the ShoppingCartBean and ProductCatalogBean classes (I've omitted a few getter/setter methods in order to reduce unnecessary clutter):
public class ShoppingCartBean
   Collection items = new ArrayList();
   IWDNode    itemsNode;
   public ShoppingCartBean(IWDContext context)
      // initialize shortcut alias for ShoppingCartItems node
      itemsNode = context.getRootNode()
                         .getChildNode("ShoppingCart", 0)
                         .getChildNode("ShoppingCartItems", 0);
   public void addItems(Collection items)
      this.items.addAll(items);
   public void removeItems(Collection items)
      this.items.removeAll(items);
   public Collection getSelectedItems()
      return ItemDTO.getSelectedItems(itemsNode);
public class ProductCatalogBean
   Collection items;
   IWDNode    itemsNode;
   public ProductCatalogBean(IWDContext context)
      // fetch catalog content from back-end
      items = new ProductCatalogBusinessDelegate().getItems();
      // initialize shortcut alias for CatalogItems node
      itemsNode = context.getRootNode()
                         .getChildNode("ProductCatalog", 0)
                         .getChildNode("CatalogItems", 0);
   public Collection getSelectedItems()
      return ItemDTO.getSelectedItems(itemsNode);
Notice that both classes delegate their getSelectedItems() implementation to a common version that's been placed in the ItemDTO class. It seems like a good place to put this type generic ItemDTO-related utility.
This DTO class could also have been used by the Command Bean version of the event handlers.. would reduce somewhat the number of loops. At any rate, the ItemDTO class shouldn't be viewed as an "overhead" to the model-based version, since it usually will have been created in the J2EE layer,for the marshalling of EJB data (see <a href="http://java.sun.com/blueprints/corej2eepatterns/Patterns/TransferObject.html">Data Transfer Object Pattern</a>). We just take advantage of what's there, and extend it to our benefit for packaging some common ItemDTO-related code we require.
// DTO made available by the EJB layer
import com.mycompany.shoppingcart.dto.ItemDTO;
public class ItemDTO extends com.mycompany.shoppingcart.dto.ItemDTO
   String code;
   String description;
   public ItemDTO()
   public ItemDTO(String code, String description)
      this.code = code;
      this.description = description;
   // returns ItemDTOs collection of currently selected node elements
   public static Collection getSelectedItems(IWDNode node)
      // create collection to be returned
      Collection selectedItems = new ArrayList();
      // loop through item node elements
      for (i = 0; i < node.size(); i++)
         // current item element selected ?
         if (node.isMultiSelected(i))
             // fetch selected item
             IWDNodeElement item = node.getElementAt(i);
             // transform item node element into ItemDTO
             ItemDTO itemDTO = new ItemDTO(item.getAttributeAsText("Code"),
                                           item.getAttributeAsText("Description"));
             // add selected item to the selectedItems collection
             selectedItems.add(itemDTO);
      return selectedItems;
Notice that the getSelectedItem() method is the only place in our model where context node navigation and manipulation actually takes place. It's unavoidable here, given that we need to query these structures in order to correctly react to user actions. But where possible, the business logic - like adding items and removing items from the cart - has been implemented by standard java constructs instead of by manipulating context nodes and attributes.
To me, using a java bean model as an abstraction for the Context is much like using EJBs as abstractions of database tables and columns:
                     abstracts away
           EJB model --------------> database tables & columns
                     abstracts away
WDP javabean model --------------> context nodes & attributes
Except that a javabean model (residing in the same JVM) is much more lightweight and easy to code an maintain than an EJB...
Before concluding, it might be worth pointing out that this alternative vision of the Web Dynpro Model in no way limits the possibility of implementing a Command Bean - if that happens to suit your business needs. You will of course always be able to implement an execute() method in your WDP Model if and when you feel the need to do so. Except that now, by breaking free of the mandatory Command Bean directive, you are allowed the freedom to ditch the execute() method if you don't need such a thing... and instead, replace it with a few well-chosen operations like getItems(), addItems(), removeItems(), getSelectedItems()... which, as we've just seen can add significant value to the javabean model made available to your WDP component.
Comments would be appreciated on this issue (if anyone has had the time/courage/patience to read this far...;). Am I alone here intrigued by the potential of this (up until now) scarcely mentionned design strategy ?
Romeo Guastaferri

Hi Romeo,
thanks for sharing this with the community. I am little bit surprised that the command pattern was understood as the only way on how to use the Javabean model in conjunction with EJBs. The command pattern blog of mine was just a very simplified example of how a functional call can be translated to a Java Bean model. Actually it was to show how the paradigm of a model works. I personally use a similar approach to yours. It seldomly makes sense to map an EJB method one to one to a model, but the javabean model must be driven by the Userinterface and represents a bridge between the business service layer and the ui. I personally even think that often it does not make sense to map RFC function like they are to the Web Dynpro Context. Most often you end up writing ZBAPIs that return structures like they are used in the UI. But if you use a java bean model as a layer in between your service layer, you are more flexible in evolving the application. Anyways design patterns for the java bean model need to be discussed more on SDN as they really add very valuable possibilities you would never have when working with value nodes alone. With the Javabean model we are back in the real OO world where things like inheritance work, things that are really not too well supported by the native WD features. I encapsulate every context of mine as javabeans. This has nothing to do with EJBs (which I am personally not a fan of) but only with the fact that I want to work with the power of the OO world.
rgds
David

Is it proper for an application module has 300 views in the data model?

Based on my understanding, all view object instances are initialized at the same time as the application module.
It follows that when an application module is associated with a user session, the queries of each view object in the data model are executed.
ie. if the data model has 325 view object instances, 325 queries will be executed.
This doesn't seem efficient:
1. As each user session only need to access a subset of the view objects (for examples 35 views), the rest of view objects need not be instantiated for that session.
2. Performance may be slow on executing all 325 queries at one time, even worse when some queries are complex queries.
Am I correct on this?
In this case, will it be better to instantiate the view objects using the view object definition at runtime instead of adding all of them to the application module at design time?

No, that's not the default behaviour.
Assuming you're talking JDev 11, the AM on it's General tab as a Tuning option where you can set the loading of the VOs to Lazy or Non-Lazy, Lazy is the default. In turn each VO on their General tab also has a Tuning option of similar nature.
Online documentation says:
Lazy LoadingSelect to choose lazy loading. In this case, the application module instance is created without any of its components. Your view object and nested application module instances will not load until the first time they are used. For example, when lazy loading is enabled, a view object is instantiated only when the application accesses it. This will make start-up time faster.
Non-lazy Loading
Select to choose non-lazy loading. Your view object and nested application module instances will load when the application starts up. For example, suppose the application module you are editing defines three view objects and two nested application modules (which appear in the Application Module Instance section of the Data Model page over the application module overview editor). When lazy loading is disabled, the application module instance is created together with all three view objects and both nested application modules.>
So in essence as you describe for each session, if we're using the Lazy setting, even though you have 325 VOs within an AM, if the user within the session only visits 35 queries, only 35 queries should fire.
Does this help?
CM.

Export with Metadata does not write EXIF Lens & GPS info

I use the Olympus E-3.
I've worked an entire project with Aperture 2 (now at 2.1.2), only to find out eventually that when exporting, aperture does not write the Lens info, and GPS section of the EXIF. This is bread and butter for me.
Did a search in the forum, and there was 1 other who encounter the same problem..
http://www.trick77.com/2009/02/01/aperture-doesnt-export-all-exif-header-info/
the workaround was to copy EXIF from the original file, using Exiftool with GUI on windowsXP. The result being that Adobe bridge and LR can read, while aperture cannot read.

I also encounterd this annoying problem... I just posted another message about this...

Where to download the sample code of Expense Tracker application

Several JSC2 tutorial articles mention a sample application called Expense Tracker. Does anyone know where to download it? The links in the articles are invalid now.
Thanks in advance

Sorry for the inconvenience. The sample code is getting updated to work with the latest release of Creator. It will be replaced soon.

Does anyone else think it is stupid that the 2nd gen of iPod touch can't update to even 4.3? Cuz none of the apps work anymore and i don't have $300 to throw down for a new one.

Yeah, I have been getting tons of updates for my apps, but since my iPod touch can only go to software 4.2.1 all of my apps have slowed down and crash,freeze, and don't get all the new things available on the other software versions. It is incredibly frustrating and kind of stupid to phase out the owners who have the older models that work just fine.

The 2G was introduced 4 1/2 years ago. That is old in electronics standards. It does not have the hardware to support a higher iOS.

PowerPivot removed table replicated into the data model on refresh

Hey
I am facing the following problem which is absolutely persistent and annoying in nature. I am using a data model created with PowerPivot with connections to three different SQL servers and 25 tables. The bug is that every time I refresh my data, a table
that was initially added to the data model (and later removed) is replicated in equivalent number of tables that use this connection, which is currently around 12 tables, so I get 12 duplicates of the same unnecessary table on every refresh, named with the
name of the schema on the SQL server that is followed by a running number. Removing these from the data model on every refresh simply takes too much time on a daily basis. The additional undesired table which is created is what is defined in the SQL query
of the connection string of this connection.
I tried to solve this problem by zipping the Excel file and modifying this SQL statement present in the connection string in the connections.xml file in a way that it would not return anything, but this always leads into a corrupted workbook.
After encountering this I have managed to avoid this problem by making sure that the initial table I'm adding to the data model will remain in the model, but I really don't want to rebuild this current model. Is there any fix for this issue without
rebuilding the data model?
Thanks for all the help in advance!

I am using 64-bit Office 2013 with the recent SP1 upgrade and the included PowerPivot plug-in on a Windows 8.1 machine.
I always create the connection by using "From SQL server" then fill in the server and log in details and use a ready SQL statement that I have written by using SQL Server Management Studio to import the initial table. For all the preceding tables
using the same server and schema, I always select it from existing connections and just paste the SQL queries required for any additional tables to the "Write a query that will specify the data to import", rather than using the table import tool.
I am not sure if it could have any effect that I've been using the type connection "From SQL server" although the database is really running on Azure (there is a possibility to select From Other sources > Microsoft SQL Azure, but the functionality
seems the same).
I don't really understand what I should edit from the existing connections section. Just to clarify, apparently the Connection String parameters can be edited from PowerPivot, but not the Command Text which can be viewed from Excel Data > Connections
> Properties, but is shown in gray with a message "Some properties cannot be changed because this connection was modified using the PowerPivot add-in."
In the data model I am using two sets of identical tables, but connected to two different servers that are running a database 1:1 in structure. Initially the problem considered only the other of these, but I accidentally reproduced it by, again, editing
the SQL query in the table that was initially imported when that connection was created (PowerPivot > Design > Table Properties). Now when refreshing I get tables that are structured as in what the "Connection Text" part of the connection would
produce, which replicated for the equivalent amount of additional tables using the same connection, so now I'm getting 12 tables (the number of tables using the same connection) each named "*schemaname1* Query", "*schemaname1* Query2",
"*schemaname1* Query3" "*schemaname2* Query" and so on.
Personally I can definitely see a pattern here. If there isn't a table matching what has been specified in the "Command Text" that was described when the connection was created, then it for some reason runs this query anyway on every table that
is using the connection.

JCo destination error while executing the webservice model

Hi,
I have explained what I have done so far and whats my issue right now.
My requirement is calling a PI interface (exposed as webservice) from webdynpro for java and setting some parameter value to the PI interface based on which our functional flow will continue.
Done so Far :
1. Created a webdynpro for java application using NWDI.
2. received the WSDL file of the PI interface and imported as "Adaptive webservice model" into webdynpro.
3. used the model and set the parameters to PI interface and executed the model.
4. I have created JCO destinations in the source system (where the application runs) to communicate to the PI system. A special user has been created and assigned in the connection for communicating.
5. Also I have created the "Dynamic Webseviceproxies" in visual admin with the same name as the JCO destinations. It had a property "URL" for which I have tested with providing both the PI server URL (Http://<Hostname>:<Port no>) and also the complete webservice URL (Which calls the WSDL file directly)
when I run the application, I get the following error.
1. Exception on creation of service metadata for WS metadata destination 'WD_RFC_METADATA_DEST' and WS interface '{<Interface Name>'. One possible reason is that the metadata destination 'WD_RFC_METADATA_DEST' has not been properly configured; check configuration.
after some exception the next error follows
2. Invalid Response Code 403 while accessing URL: <The URL which I have provided in the webservice proxy in Visual admin tool> Response Message: Forbidden.
after some lines of exception from PI server the next error follows.
3. Error: You are not authorized to view the requested resource
My Question :
1. Do I miss anything in Configuration?
2. Is my way of approach wrong?
3. Any additional authorization needed?
Kindly provide some ideas and inputs.
Regards,
Mahendran B.

Dear Mahendran
JCO destination will not used for the Web Service Model. While creating the webservice model, you need to use the logical destination which you have created in the Visual Admin.
Please refer to the Secured WebServices II and verify currently used webservice logical destination How To Reimport Web Service Models in Web Dynpro for Java
You can also refer to
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/900bbf94-a7a8-2910-e298-a651b4706c1e?QuickLink=index&overridelayout=true
Hope it will helps
Best Regards
Arun Jaiswal

Can i insert a sim card in the Ipad model A1395

CAN I INSERT A SIM CARD IN THE IPAD MODEL A 1395

No it is the Wi-Fi only model...
http://www.everymac.com/systems/apple/ipad/specs/apple-ipad-2-wi-fi-specs.html

Option Show Source/Target Name "on" in the logic model

In the data modeler 2.0.0 was the option Show Source/Target Name “on”. Where do I find it in data modeler 3.0.0 ?

Hi,
Right click on Logical diagram and from context menu select Show->Labels
Regards,
Ivan Zahariev

Tracking theives, does the 3g model's gps tracking justify the added cost?

Similar Messages

Maybe you are looking for