Stephen Lebans Tools Compatability

[DawnTreader]

Hello All

i have great need for 3 tools of Stephen Lebans to work together in the same
database system. i need to know a few things about the tools. the 3 tools are
the save and restore relationships window layout tool, the relationship and
query to bitmap utility, and the select relationship tables tool.

are these three tools all compatible with access 2003 with service pack 3?
and when importing each tool to my database do i need to bring in the both of
the modGet-SetScrollInfo modules from 2 of the databases as one? should i
merge it, overwrite it or rename it?

additionally if i import these do i import them to my backend or my frontend?

i have tried them out already, but i got a lot of problems with the second
one i imported to the same db that already had the modGet-SetScrollInfo
module. i thought the 2 different modGet-SetScrollInfo modules were the same,
just the same code in 2 different dbs.

anyones help and suggestions would be appreciated. especially Stephen's...

 

[Stephen Lebans]

Back ends are for data, FE are where you would place my code modules.

All you should have to do is rename one of the modGet-SetScrollBarInfo
modules.
I am usually quite careful to keep all variable API declarations declared
Private within each module.

As for the WIndowToBitmap solution, I have a much improved solution here
that outputs the entire Relationship window to a single page PDF document.
Now with this single page PDF doc, you can output the diagram, using the
many options for scaling within your PDF reader APP, to individual sheets of
whatever paper size your printer supports. Even better, you can EMail the
document to your local print ship, UPS/Business Depot/Whatever and output
the single page onto a large format printer. It's very impressive to see a
large relationship diagram on 2ft x 3ft single page!

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[DawnTreader]

Hello, Anyone?

 

[Douglas J. Steele]

Stephen posted an answer to your question a week ago. (see
http://groups.google.com/group/microsoft.public.access.modulesdaovba/msg/aabf0cae852fc5ad
if you missed it)

Did it not help?

 

[DawnTreader]

OH!

rats i dont normally use the google groups i usually post at the microsoft
interface. hmmm

does the google group keep all the posts that are on the microsoft one?
maybe i should move over there?

 

[Douglas J. Steele]

All posts to all newsgroups are archived in Google. However, I wouldn't
necessarily moved to Google.

 

[DawnTreader]

Back ends are for data, FE are where you would place my code modules.

All you should have to do is rename one of the modGet-SetScrollBarInfo
modules.
I am usually quite careful to keep all variable API declarations declared
Private within each module.

As for the WIndowToBitmap solution, I have  a much improved solution here
that outputs the entire Relationship window to a single page PDF document.
Now with this single page PDF doc, you can output the diagram, using the
many options for scaling within your PDF reader APP, to individual sheets of
whatever paper size your printer supports. Even better, you can EMail the
document to your local print ship, UPS/Business Depot/Whatever and output
the single page onto a large format printer. It's very impressive to see a
large relationship diagram on 2ft x 3ft single page!

--

HTH
Stephen Lebanshttp://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.


Hello All

Thank you for your response!

After reading i tried out renaming the module and the modules played
well together.

another question relating to the "where" to import them. taking a big
step back however to some basics about be and fe design.

if i have the tools in the frontend how do i "manage" my relationships
in the back end? up till now i have been creating relationships in the
backend and arranging that window so that i can see the relationships
there. your statement about the backend for data and frontend for code
makes sense, but where do i make my relationships? it almost sounds
like the relationships are created in the frontend from that
statement. i know that i can play around with them in both, but the
only place i create new ones are in the backend. is that the normal
way of doing things or am i missing something in my knowledge about
be / fe development?

i was using the select tables in the relationship window tool to help
me to find the tables and move them to areas so that i can start
working on some structure changes, but that meant i needed the utility
in the backend. is the backend the wrong place to do relationship
creation and managment?

 

[Klatuu]

Relationships belong with the tables in the back end.