Search results

Ok, Well now that resolves that error, but there is more! Now the declarations are not causing problems, but the line Set Con = CurrentProject.Connection gives a type mismatch error. Any idea what the problem is. Appreciate the effort anyway boss. This seems a lot harder than it should be I...

Thanks, I gave it a try but I get an error on Dim Rs As ADODB.Recordset "User- defined type not defined". Do I need to use a special reference or something?

Hello again My readings tell me that access reports do no support the recordset property. This appears to cause problems! I want users to be able to set the record source for their reports, as well as the group levels. Anybody know how to use these user defined settings to pull a identical...

Yeah I've tried that, if I use Set MyRstReport = MyDbs.OpenRecordset(me.recordource) it works, but the recordset is not sorted in the same way as the recordset used by the report. I need to ensure that my code is looking at the same record as the report on each new Page event. Is there a way to...

Hello, all hope somebody can help with this. I have a report, and in its header I want to display field values from a table. This is a different table to the reports records ource. However, the record read from the table depends on a field value from the reports record source. I presume there is...

Have tried this I have tried using, Dim MyRstReport As Recordset Dim MyDbs As DAO.Database Set MyDbs = CurrentDb Set MyRstReport = Me.Recordset but it gives an error "This feature is not available in a MDB"

Hello, I think I'm trying to do something similar. I have a report, and in its header I want to display field values from a table. This is a different table to the reports recordset. However, the record read from the table depends on a field value from the reports recordset. I presume there is a...

Indeed why not. Thanks for that.

Hello all, I am setting up an access 2003 database in a Client/Server configuration. All dat entry is done through queries, forms are not used. I am wondering if it's possible to prevent users in the client database (Or a copy of it) from creating new queries that hang of the linked tables. I...

Ok Guys, I really need time to digest all this properly. I certainly have improved my database structure drastically from with your help. But I'm sure as I study these posts i'll be able to make further improvements. Thanks a lot for the help.

This is because Access lacks some of the requisites of a true Object Oriented environment - Inheritance, polymorphism etc. I believe there are third party tools that can help with regard to Inheritance. Whoa, can you explain? Is there really a problem with just finding and replacing an sql...

Ok dudes, I'll check out your suggestions, sounds good. I'm off to Malta myself tomorrow so I'll be quiet for the week. Don't go away though I'll be back!

UNLESS.... you have actually succeeded in defining a device table in such a way that for some devices you have no requirement for supplemental data. And THAT is desirable Sorry, this is what I said was correct.

Yes, this is correct. With parent/child structures, you must ALWAYS enter data to the main table first if you wish to enforce referential integrity And just on this point. I now no longer need to use RI as Autonum is now the primary key with the foreign key being a long integer in the child...

Sorry, can you tell me what this means? Set rs = db.OpenRecordset("DEPENDENCIES") You mean I should have a tabe called DEPENDENCIES? Thanks a lot

Ok thanks, That code looks good I'll give it a try.

Thanks Again Doc Man, Quote: (Unless the overlapping tables, only overlap the Autonum and have completly different fields). This doesn't happen. In the overlapping tables, the key is FOREIGN and therefore depends on something outside the table. (The entry in the main table, e.g.) There WILL...

Progress? Yes, Thats good Doc man, What you say about relavence, makes me think that at least my "main table" is not in too bad shape. I believe all the fields obey the rules you outlined. The automumber PK I am now using will have no meaning outside the database. In my mind it simply replaces...

I was silly Yes I was being silly, you just make the related field in the secondary table a number, and not an autonumber I think?

Boooo! Ok, Thanks anyway.