All postings to this forum are published immediately. The owner of this site is not responsible for anything written in this forum. However, we are editing the messages regularly to enhance the usability of this forum. When editing a message we are deleting all personal information like addresses and parts of the author's name other than the first name.

blueshell Forum

Add a new thread

Converting VS2005 SQLEXPRESS *.mdf to *.mdb -- 2007-03-12 19:22, Emmanuel

A bit of breakthrough- Converting VS2005 SQLEXPRESS *.mdf to *.mdb -- 2007-03-12 23:35, Emmanuel

how can i connect my sql database from vb.net to access database 2000 -- 2007-02-12 11:59, andrew

Coverting sql to access -- 2007-01-05 13:54, Ruth

This way you can convert from mySQL to Access -- 2007-01-06 15:16, Harry

export all tables -- 2005-05-10 11:31, StXh

Sorry -- 2005-05-11 17:07, Harry

Scrolling problems -- 2005-03-13 09:09, Len Heard

There is a difference by design -- 2005-03-14 18:18, Harry

Blueshell ErrorGuy Expires? -- 2005-02-22 04:15, Cameron

Please download the latest release -- 2005-02-22 18:36, Harry

Still expired - 7th February 2007 -- 2007-02-07 11:07, Grant

Fresh release available -- 2007-03-24 17:21, Harry

atb properties makes VB6 crash !! (Very frustrating) -- 2005-02-15 01:16, Len Heard

Please give me more info -- 2005-02-15 19:34, Harry

All OK again... ( I Hope ) -- 2005-02-25 15:20, Len Heard

Invalid Key -- 2005-02-14 16:45, Len Heard

Answered directly -- 2005-02-15 19:39, Harry

Help for VB5 and Blueshell -- 2005-02-04 20:03, Gchienna

Yes, bAt supports VB5/Access2000 -- 2005-02-05 13:32, Harry

Table Datatype MS SQL Server and MSDE -- 2005-02-04 05:26, Sretlaw

Two reasons for your experience -- 2005-02-05 13:06, Harry

Hi Sretlaw,

There are two reasons for your experience:

1. Currently, blueshell Data Guy (bDg) always uses autoincrement on any type that supports autoincrement. I agree, that this can be misleading and we're considering to change this behaviour. But there's always an escape: Choose the common type Long that maps to SQL Server's int.

2. In order to provide easy transfer from one database to another (e.g. from Oracle to SQL Server), bDg maps types. That is the reason why your _varchar columns are displayed as _text and _int columns are displayed as Long. Don't worry - they are still SQL varchar and int respectively. It is on our to-do-list to display the native types while retaining the mapping capabilities.

Thanks for your input!

- Harry

Post a reply

Your name

Your e-mail

Optional. We are only using this to give you feedback. The e-mail is not published at this forum or elsewhere. Your data will be treated in the strictest of confidence, and will never be shared with any third party. For more information read our privacy statement.

Your message

BoldItalicSmall
H1 H2 H3
Ruler
1 return = line break, 2 returns = new paragraph

Your caption

Please specify a summarizing caption of your message, not just "RE: bla bla"

blueshell: New Service Releases -- 2004-09-20 20:07, Harry

Impressive tool; thanks to give it for FREE! -- 2004-09-24 08:10, Bernie Davest

bAt -- Automatic Form View -- 2004-08-19 04:27, Marcelo

4 steps to get it work -- 2004-08-19 18:45, Harry

Help! Help! -- 2004-07-20 08:17, Narong CHIN

Please give me some details -- 2004-07-24 09:56, Harry

Ora-12500 error -- 2004-05-06 15:23, Fast2catch

Problems with your Oracle? Try bDg to test! -- 2004-05-21 13:56, Harry