A thought came up when I built a simple website for displaying points in a indoor fotball tournament a couple of weeks ago and it was actually a mistake when I was stressed getting data into the system that rendered an error for me that is the source to the question in the title

I wrote Timmele GoiF in one place in the system (id of a team in the tournament) and Timmele GoIF (capital i in GoIF) and of course the system did not work since i used a bit of scripting in the page.
As a human I know, of course, that this is the same team since I know the team. But should a system know this?

Of course, I should not have used the teams name as an ID in the system, it would have been easier/better to have used a numeric id or something that is better for the database engine to index and for, in my case, scripting to understand.

But if names is an identifier in a system, the question arise:
Is a capital version of TIMMELE GOIF the same as the lower case timmele goif?
In older system, for example the ERP Garp, it is a distinction but in more modern SQL server based systems (depending on setup of course) there is no distinction.

How should it be? What is the best, integrationwise?

A lot of questions and, Im sure, a lot of answers.

In my world it should be the same if I want to integrate between two system and if it is a standalone system it could be different since I dont have to talk to others but myself (myself being the system)

If you enjoyed this post, make sure you subscribe to my RSS feed!

If you see this post it means that BlogEngine.NET 1.6.0 is running and the hard part of creating your own blog is done. There is only a few things left to do.

Write Permissions

To be able to log in to the blog and writing posts, you need to enable write permissions on the App_Data folder. If you’re blog is hosted at a hosting provider, you can either log into your account’s admin page or call the support. You need write permissions on the App_Data folder because all posts, comments, and blog attachments are saved as XML files and placed in the App_Data folder. 

If you wish to use a database to to store your blog data, we still encourage you to enable this write access for an images you may wish to store for your blog posts.  If you are interested in using Microsoft SQL Server, MySQL, VistaDB, or other databases, please see the BlogEngine wiki to get started.

Security

When you've got write permissions to the App_Data folder, you need to change the username and password. Find the sign-in link located either at the bottom or top of the page depending on your current theme and click it. Now enter "admin" in both the username and password fields and click the button. You will now see an admin menu appear. It has a link to the "Users" admin page. From there you can change the username and password.  Passwords are hashed by default so if you lose your password, please see the BlogEngine wiki for information on recovery.

Configuration and Profile

Now that you have your blog secured, take a look through the settings and give your new blog a title.  BlogEngine.NET 1.4 is set up to take full advantage of of many semantic formats and technologies such as FOAF, SIOC and APML. It means that the content stored in your BlogEngine.NET installation will be fully portable and auto-discoverable.  Be sure to fill in your author profile to take better advantage of this.

Themes and Widgets

One last thing to consider is customizing the look of your blog.  We have a few themes available right out of the box including two fully setup to use our new widget framework.  The widget framework allows drop and drag placement on your side bar as well as editing and configuration right in the widget while you are logged in.  Be sure to check out our home page for more theme choices and downloadable widgets to add to your blog.

On the web

You can find BlogEngine.NET on the official website. Here you'll find tutorials, documentation, tips and tricks and much more. The ongoing development of BlogEngine.NET can be followed at CodePlex where the daily builds will be published for anyone to download.

Good luck and happy writing.

The BlogEngine.NET team

If you enjoyed this post, make sure you subscribe to my RSS feed!

B2B, trade of products or services, between a wholesale and a retailer often consists of a varying transaction size as opposed to manufacturer -> wholesale which often work with big transactions. 

The wholesale is the supplier and the retailer is the customer in this case.

Being a supplier in this kind of B2B chain is less complex since there is often refined products being traded.

The customer is in his turn often performing directly against end customers (and ends the supply chain going from B2B to B2C)

Trading documents or information between the organisation is often sent through fax or some kind of integration message between procurement systems or directly between ERP systems.

If you enjoyed this post, make sure you subscribe to my RSS feed!