Recent content by misunders2d

:( probably it's the time to get rid of DAO finally.. However, taking in account that direct sql usage (DDL) in access is incomplete, lacking some basic fuctionalities, DAO was a nice way to smooth it. ADO has huge advantages, but correct me if there's no coder left still using DAO...

Hi, everyone.. :) As always, i have antother tricky issue :) Though I am not so sure this question fits the forum, I hope some access users have encountered the same obstacle and have suffered like me. ;) The problem is related to the xml export: when u export xml from query/report which has...

Hey ghudson, It seems you've missed that the box is unbound thus the afterUpdate doesn't fit so well ;) Nirious, i am not sure what kind of behaviour you were talking about. The validation rule proposal by ghudson works great! Although now you specify the validation rule of the control and not...

Hi, dude.. ;) Have you tried this one: Me.frmSub.Form.Recordset.Delete Me.frmSub.Form.Recordset.MoveNext

Hi, goldenorb82! :) As a solution, you can: 1)empty the initial tables by delete query (no way deleting record by record), for instance DoCmd.RunSQL "DELETE * FROM tableName" 2)import new table with temporary name by DoCmd.TransferDatabase acImport 3)select all data into initial table...

Hope it will work :)

:) As far as i remember AND is logic operator in vb, which returns a boolean value. Try replace this by: If ProdScore = 1 Then e.BackColor = 8454143 d.BackColor = 8454143 Else e.BackColor = -2147483633 d.BackColor = -2147483633 End If and don't forget to use switch structure :)

..almost forgotten, to see the results of the back-end update in the front-end you should relink the tables. It can be done from code by: Public Sub reLink(strFileName As String) Dim db As Database Dim tDef As TableDef Dim tDefs As TableDefs Set db = CurrentDb Set tDefs =...

Hey Happy, i know these posts start annoying you, but changing database structure from the front-end is not so highly recommended. Anyway, if you want to update the db structure from the front end application you should use: Dim db as Database Set db=OpenDatabase(strDbName) db.Execute "ALTER...

Hi, once more! :) As far as I understood it's impossible to enforce cascades via DDL in Access. However, there's always a bypass. :) And that's done by DAO: Dim db As DAO.Database Dim rel As DAO.Relation db = OpenDatabase(strFileName) Set rel = db.CreateRelation(strRelationName...

Hi, all... :) I need to create cascade relationship on fly. I've succeeded to create the relationship by: ALTER TABLE tName ADD CONSTRAINT fk_id FOREIGN KEY(ID) REFERENCES tPrimary(ID) and even succeeded to check the referential integrity by: ALTER TABLE tName ADD CONSTRAINT fk_id FOREIGN...

Is it possible Hey, guys. I start thinking this option is impossible for the direct implementation. May be someone has an alternative solution. I've already thought about moving the unneeded groupping to the lowest level and playing with the visibility of fields. However it doesn't seems to be...

hey :) I am trying to implement a kind of dynamic report construction. I know it's possible to add grouplevel from code, however i have some troubles with deleting groupping levels. For instance, i have: grouplevels(0)... grouplevels(n). However i decide i need n-1 levels - how can i change...