Greetings! Welcome to my Dynamics AX 7 and related MS Technologies blog.
Total Pageviews
Search This Blog
Tuesday, February 26, 2008
Dynamics AX 2009
Interface: http://64.233.179.104/translate_c?hl=de&langpair=ru%7Cen&u=http://blogs.msdn.com/aeremenk/archive/2008/01/14/7108028.aspx
TimeZones: http://64.233.179.104/translate_c?hl=de&langpair=ru%7Cen&u=http://blogs.msdn.com/aeremenk/archive/2008/01/31/7339961.aspx
Working with Several companies:
http://64.233.179.104/translate_c?hl=de&langpair=ru%7Cen&u=http://blogs.msdn.com/aeremenk/archive/2008/01/16/7128142.aspx
Database:
http://64.233.179.104/translate_c?hl=de&langpair=ru%7Cen&u=http://blogs.msdn.com/aeremenk/archive/2008/01/15/7118429.aspx
Transfer selected record from one grid to another
Refreshing a datasource
Friday, February 22, 2008
Delete transactional data using SysDatabaseTransDelete class
SysDatabaseTransDelete deletes the transactional data and makes it clean for testing purpose. It retains all the setup and master data. Handy to do regression testing where transactional data has to be deleted and re-tested again.
Using Like in x++ select statement
Visit the below link:
http://www.microsoft.com/Businesssolutions/Community/Newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.axapta.programming&lang=en&cr=US
Thursday, February 21, 2008
Worth the Wait: SQL Server 2008
http://www.quest.com/landing/?ID=1252&AdCode=MSSQLTips486x60BannerChangeDirector22008
Wednesday, February 20, 2008
Launch Event of Microsoft Windows Server 2008, Visual Studio 2008 and SQL Server 2008
http://www.microsoft.com/heroeshappenhere/register/default.mspx
I'm lucky to get the confirmation and the event will be on 4th March 2008, Bangalore (Rex Theatre). Will post more about it once I come from there.
Thursday, February 14, 2008
Concept of a new IDE Visual Studio 2010
Things to come.....
http://www.codeproject.com/KB/cs/concept_ide.aspx?fid=183427&fr=26#xx0xx
Tuesday, February 12, 2008
Cleared Exam MB6-508 Morphx - Development Introduction
The questions revolve around these areas:
General Microsoft AX Architecture – 18%
Understanding of 3-tier Architecture
Understanding of AOS Knowledge of Layer Technology and how to Work with Them Understanding of Label System and Creating Label Files
Development Tools - 18%
General Knowledge of AOT
How to use Intellimorph
How to Import/Export Objects
Debugging Techniquest
Visio
Application Objects– 21%
Creating Data Dictionary Objects
Creating and Working with Forms
Setting Up Projects
Creating and Working with Reports
Creating and Working with Queries
Creating and Working with Menus and Menu Items
Utilizing the Security Structure
Utilizing the Configuration Structure
Table Collections and Virtual Companies
X++ Development – 27%
Data Manipulation/Accessing the Database
Working with Maps
Interacting with the User
Working with Data Models
Working with Class Models
AX-specific
Select Techniques
Best Practices – 16%
Using Naming Conventions
General X++ Coding Standards
Using Validation Techniques
Preparation Materials
Go through the e-learning courses :
8623A_AX40_ENUS_DEVI
8633A_AX40_ENUS_DEVII
https://mbs.microsoft.com/partnersource/communities/training/Certifications/exampreparation/AX4_DevIntro_prep.htm
Microsoft Dynamics Axapta Video 2009
https://mbs.microsoft.com/partnersource/products/axapta/newsevents/news/AXvideo_kirill.htm
Monday, February 4, 2008
Getting Started with my first LINQ program
{
class Program
{
static void Main(string[] args)
{
int[] numbers = new int[7] { 0, 1, 2, 3, 4, 5, 6 };
var numquery =
from num in numbers
where (num % 2) == 0
select num;
//3. Query Execution
foreach (int num in numquery)
{
Console.Write("{0,1}", num);
}
}
}
}
LINQ - Language Integrated Query
LINQ is a methodology that simplifies and unifies the implementation of any kind of data access. LINQ does not force to use a specific architecture but it facilitates the implementation of several existing architectures for accesing data.
You can download free e-book regarding LINQ from the following site:
http://introducinglinq.com/
Friday, February 1, 2008
Interface must extend interfaces not classes
Solution
Closed and Re-opened AX and then compiled again and the error vanished.
SQL 2005 Database State
The following table defines the database states.
State | Definition |
---|---|
ONLINE | Database is available for access. The primary filegroup is online, although the undo phase of recovery may not have been completed. |
OFFLINE | Database is unavailable. A database becomes offline by explicit user action and remains offline until additional user action is taken. For example, the database may be taken offline in order to move a file to a new disk. The database is then brought back online after the move has been completed. |
RESTORING | One or more files of the primary filegroup are being restored, or one or more secondary files are being restored offline. The database is unavailable. |
RECOVERING | Database is being recovered. The recovering process is a transient state; the database will automatically become online if the recovery succeeds. If the recovery fails, the database will become suspect. The database is unavailable. |
RECOVERY PENDING | SQL Server has encountered a resource-related error during recovery. The database is not damaged, but files may be missing or system resource limitations may be preventing it from starting. The database is unavailable. Additional action by the user is required to resolve the error and let the recovery process be completed. |
SUSPECT | At least the primary filegroup is suspect and may be damaged. The database cannot be recovered during startup of SQL Server. The database is unavailable. Additional action by the user is required to resolve the problem. |
EMERGENCY | User has changed the database and set the status to EMERGENCY. The database is in single-user mode and may be repaired or restored. The database is marked READ_ONLY, logging is disabled, and access is limited to members of the sysadmin fixed server role. EMERGENCY is primarily used for troubleshooting purposes. For example, a database marked as suspect can be set to the EMERGENCY state. This could permit the system administrator read-only access to the database. Only members of the sysadmin fixed server role can set a database to the EMERGENCY state. |
Suspect database state
I found this link useful:
http://www.sqlusa.com/bestpractices2005/markedsuspect/