If you want your android's device (Phone or tablet), with jellybeans, honeycomb, etc, load full web pages instead of the mobile version, do the next steps:
1. Open the browser on your device
2. In the address bar, type: about:debug then press enter
3. Open the browser's settings (the icon in the top-right corner, it looks like four horizontal lines) then selecting "Settings" from the drop-down menu
4. Select the Debug section
5. On the right side of the screen, select UAString then select Desktop as the new option
6. To exit the debug mode in the browser, press the back button in your device
7. In the browser's address bar, type again "about:debug" then click enter
Now your device is ready to display full web pages, instead of mobile ones.
This is a blog where you are going to find tips or solution that are going to be helpful in the technology environment.
Wednesday, January 30, 2013
Thursday, January 24, 2013
The connection to adb is down, and a severe error has occured
If you get the error in Eclipse:
"The connection to adb is down, and a severe error has occured"
When trying to debug your application in your device, that means the adb server was not initialized right, to solve this problem, do the next steps:- Be sure Eclipse is not running
- Open the command prompt in the Android SDK platform-tools directory
- Type the command: adb kill-server, to stop the server
- Restart the server with the command: adb start-server
- Start Eclipse
Now you should be able to test you app in your device
Monday, January 21, 2013
Warning: the following job steps cannot be reached with the current job step flow logic
If you get this error, I would guess that you have somehow set another step instead of the first one as the starting step in the
package.
To solve this problem:
- Right click on the Jjob and select "Properties"
- Click on the "Steps" option
- Below the Job list, see the "Start step" option, verify the step showed is the first one
- Click the Ok button so save any modifications
Tuesday, November 6, 2012
70-480 Certification for free - Programming in HTML5 with JavaScript and CSS3
All you need for FREE for the certification:
70-480: Programming in HTML5 w/ JavaScript + CSS3
FREE voucher code: HTMLJMP
Free Training from Microsoft
Free eBook - Programming Windows 8 Apps with HTML, CSS, and JavaScript
Free Events - Microsoft Learning Partners
70-480: Programming in HTML5 w/ JavaScript + CSS3
FREE voucher code: HTMLJMP
Free Training from Microsoft
Free eBook - Programming Windows 8 Apps with HTML, CSS, and JavaScript
Free Events - Microsoft Learning Partners
Monday, August 6, 2012
VB6 Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection
If you are getting the next error on your VB6 applications when trying to run selects:
Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection
Looks like the problem is in the ODBC connection. Be sure you have selected the check boxes:
Use ANSI quoted identifiers
Use ANSI nulls, paddings and warnings
Friday, August 3, 2012
VB6 No creatable public component detected
If you get the error "No creatable public component detected" when trying to
compile a new VB application like the one below, you need to change the Instancing value because it is private.
Just change the instancing to Multiuse or GlobalMultiuse:
Just change the instancing to Multiuse or GlobalMultiuse:
Tuesday, July 17, 2012
Controls dynamically added in ASP.NET are lost after a postback
If you are loosing your controls added dynamically to a web page after a full or partial postback, is because you are not creating them in the Page.Init.
According to the ASP.NET Page Life Cycle, PostData (all values inputed on the client side) is applied between the Page.Init and Page.Load, so, if you add a control in the Page.Init, they will not lose their state and you don't have to recreate them.
According to the ASP.NET Page Life Cycle, PostData (all values inputed on the client side) is applied between the Page.Init and Page.Load, so, if you add a control in the Page.Init, they will not lose their state and you don't have to recreate them.
protected void Page_Init()
{
Control ct = ParseControl(" ");
Page.Controls.add(ct);
}
Subscribe to:
Posts (Atom)