Cant find diagram property

Hi,

i set up an diagram with crystal reports and Visual Basic 2005.
Everythink works fine, but I got in trouble with a font size property of the so called "datalabel". I did not find the property where I can set the fontsize to a smaller one. To demonstrate my problem I attached a picture with the meant label surrounded.

Can anybody help me?Ok, I asked the supprt of crystal. It is not possible with the visual studio integrated version, you have to update to XI :(

Cant expand SQL6.5 database

I have a SQL 6.5 database where I need to expand the size
of a database. The database device has been expanded but I
seem to be missing something when it comes to expanding
the database.

The database in question is named edidata. When I enter
the Expand Databases screen I see my database named
edidata. At the top of the screen are two drop down boxes
one lableled Data Device and the other is Log Device. In
the the Data Device drop down I see only

none
new
Database x
Database y

(But not edidata)

I have several hundred Meg available on the device and
additionally lots of Disk space not yet allocated.

When I pull up the Log Device drop down this database device name
does appear. If I attempt to expand any of the other 3 databases on this server I'm able to see this database device name in the drop down list.

In case it matters I do have both a Data base
and Log contained within this Database device.

Any help would be greatly appreciated.

Thank you
..Having mixed use devices always complicates things. (If you have run into the point where the Log starts, I think you may be out of luck for additional data space on that device for that DB. Other DBs would still be able to use free space beyond the Log boundary within the device.)

The tsql to add 500MB (if available) should be something like:

Alter DataBase edidata
On Edidata_DeviceName = 500
Go

(You would have to use the correct names, of course.)|||You might consider creating another device called something like EdiDataLogDevice, (designating it for Log use only), and moving the existing EdiData Log there (from its current location).|||As you can tell I don't do a great deal of DBA work with MSSQL. I know how to create the Database device but I'm not sure of how to move the Log to the new device. Does anyone have any pointers?|||Originally posted by Dale Marthaller
As you can tell I don't do a great deal of DBA work with MSSQL. I know how to create the Database device but I'm not sure of how to move the Log to the new device.

Q1 Does anyone have any pointers?

A1 I rarely do anything with 6.x Sql Servers anymore, (other than a rare upgrade), but I'd probably start by testing the following on a dev server / dev DB (should work):

/* I guess I'd do something Like this (#0 Full Backup Dump!) */
/* 1 Create the extra device (use an appropriate size, not 2048): */
Disk Init
Name = 'EdiDataLogDev',
PhysName = 'c:\EdiDataLogDev.Log',
VDevNo = 8,
Size = 2048
Go
/* 2 Make sure the extra device is there: */
exec sp_helpdevice
/* 3 Check out the existing DBs, existing DB Log / LogSpace: */
exec sp_HelpDB
exec sp_HelpDB EdiData
exec sp_HelpLog
dbcc Sqlperf(LogSpace)
Go
/* 4 Add the new device to the DB: */
Alter DataBase EdiData On EdiDataLogDev
exec sp_HelpDB EdiData
/* 5 Mark the new device on the DB for Log Only: */
exec sp_LogDevice EdiData, EdiDataMixDev
Go
/* 6 Verify the changes, carefully note the following: */
exec sp_helpdevice
exec sp_HelpDB EdiData
/* 7 Then create some dummy tables, populate them in EdiData, dump the log etc. (flush the log from the old device): */
Dump EdiData With Truncate_Only
/* 8 Verify the changes, carefully note the following:*/
exec sp_helpdevice
exec sp_HelpDB EdiData
/* 9 EdiDataLogDev should be Log Only, and the original Dev should be Data Only */|||Thank you I will tackle this today.

Can't connect to full MSDE 2000 (urgent)

I think I've "filled" an MSDE 2000 SP3a database to its maximum 2GB size, and now can't connect to it.

OSQL gets an "insufficient file size" error.

Have also tried to connect via Ent Mngr, and get database is "suspect" error.

How can I connect in order to purge some data?

Thanks!!!!

DT

When connecting using Enterprise Manager, which database is the suspect? Search for the database file in your file system (databasename_.MDF) and check whether you do have enough free space in the disk containing the MDF file. If not, try freeing up some space on that disk just for you to do maintenance. Then you can do a couple of things - truncate the log and shrink the file, move the database file to a different drive, extend the volume by adding disk, or free up some space by deleting large files on the disk.|||

We know which database, and there's plenty of room on the disk.

The problem isn't that we don't know how to make the database smaller... it's that we can no longer connect to it in order to truncate/shrink.

Can you recommend a recovery tool?

DT

|||

I was able to attach the database to a SQL2K instance, and do a backup.

Problem resolved