Comments
Sort by recent activity
Hello Ben!
Yes, the regex is $[Address]
The datatype of the source column (Address) is varchar(100), is not nullable and is being populated by the Address Line (Street Number) generator.
The datatype of the destination column is varchar(1000), not nullable and is being populated by the Regex expression which contains $[Address].
BTW, I have also noticed that adding a FK column to the regex window causes this column in the preview pane to gray out and display what appears to be a lock icon - looks like a link of a chain. Is this expected behavior?
David / comments
Hello Ben!
Yes, the regex is $[Address]
The datatype of the source column (Address) is varchar(100), is not nullable and is being populated by the Address Line (Street Number) generator.
The dataty...
Hmmmm.....
We are using Sql Server 2005 SP2.
I did what you did and it worked for me also. I noticed you had an int ID column, our table is using a GUID as the PK. I also tried it with a GUID PK and it still worked.
I will send you the schema and project file. I have your email address from a previous interaction. The schema includes some Full-text search SQL which you may wish to comment out rather than try to get it configured to work. I included in the script it so you would know that it exists. The script I will send you was generated with Microsoft's Database Publishing Wizard.
As always, thanks for the help.
David / comments
Hmmmm.....
We are using Sql Server 2005 SP2.
I did what you did and it worked for me also. I noticed you had an int ID column, our table is using a GUID as the PK. I also tried it with a GUID PK an...
I am kind of surprised by the lack of any response to this post. Does this mean that nobody has ever encountered this problem? Or am I not clear in the description of the problem? / comments
I am kind of surprised by the lack of any response to this post. Does this mean that nobody has ever encountered this problem? Or am I not clear in the description of the problem?
No reply necessary.
I would like to add my 2 cents on this feature - it would be VERY handy. I have a table where there is a CaseType column and a CaseSubType column. Some CaseType/CaseSubType value combinations are not valid. So to be able to constrain the value of CaseSubType based on the value of CaseType would be a great feature. / comments
No reply necessary.
I would like to add my 2 cents on this feature - it would be VERY handy. I have a table where there is a CaseType column and a CaseSubType column. Some CaseType/CaseSubType valu...
Shortly, after posting the previous reply in this thread, I encounterd this problem in SQLGEN 1.1. I changed the connection string in a file that I had been editing (and saving) and clicked Generate Data button.
The resulting report started with:
Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at e.a() at e.b() at t..ctor(ConnectionProperties connectionProperties, SDGTable sdgTable, CountAction countAction) at aw.a(CancellableController , Int32 , Int32 , ConnectionProperties , GenerateAction , SqlConnection , SDGProject , GenerationReport )
Repeated attempts in same session failed. Restarting the app fixed the problem. / comments
Shortly, after posting the previous reply in this thread, I encounterd this problem in SQLGEN 1.1. I changed the connection string in a file that I had been editing (and saving) and clicked Generat...
I have seen this in the 1.0 version when making a database change while the app is running, refreshing the schema in the UI and then generating data. The database changes included column name change, column type change and removal of foreign key - all done sequentially during the same session of SQLGEN.
I am using 1.1 now but have not been in a position to need to do any database changes while working with SQLGEN.
Hope this is of some help. / comments
I have seen this in the 1.0 version when making a database change while the app is running, refreshing the schema in the UI and then generating data. The database changes included column name chang...