home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.paradox      To crash or not to crash, asks Borland      9,834 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 9,343 of 9,834   
   Dominick DiMantova to Leslie Milburn   
   Re: Overview of Paradox database structu   
   01 Aug 08 12:35:02   
   
   From: dominickdimantova@comcast.net   
      
   Hello; I have experience with RDMS, SQL Server 2000/2005, DTS, etc., so I   
   have the knowledge of relational database concepts and design: I know the   
   difference between an OLTP and an OLAP database, I know the difference between   
   a star and a snowflake sheme within a multi-dimensional OLAP database. So,   
   I'm no newbie here. But I did get the basics of a paradox relational database   
   structure so that I can relate this information to my experience with MS   
   Access so that I can succeed in the migration effort of Paradox into Access.   
      
      
      
      
   "Leslie Milburn"  wrote:   
   >Hi Dominick,   
   >   
   >Please do not be offended with this post but I feel I must be honest with   
      
   >you.   
   >   
   >Firstly as a person who has hired and fired many people over the years I   
      
   >would *not* be fooled in the interview process into believing you would   
   know   
   >anything worthwhile about Paradox. The *minimal* scraps information Michelle   
      
   >has provided will make no difference at the end of the day as it is trivial   
      
   >and in fact could acctually trigger exposure of your lack of knowledge with   
      
   >a follow-up question. What will make a *big* difference is that I would   
      
   >catch you out lying to me and so you would be instantly ruled out for the   
      
   >job on that basis alone regardless of your other experience.   
   >   
   >Having said that, given the brief job requirements you have posted it   
   >appears that the role is one of data migration rather than one of specific   
      
   >Paradox knowledge. So the requirements (in my mind) will be to have an   
   >*excellent* understanding of Relational Database Design. You should be able   
      
   >to sit down and draw the Relational Database Structure from the paradox   
      
   >table contents alone - ie have an understanding of pure data.   
   >   
   >However, reading your initial post, two things come immediately to mind:   
      
   >Firstly the type of questions you have asked indicate you do not have that   
      
   >knowledge otherwise you would not have asked/raised some particular points.   
      
   >Secondly it appears you cannot take criticism very well. One of the things   
   I   
   >do when interviewing is I do a google search on the person applying for   
   the   
   >job. I know its is sneaky and usually nothing turns up - but every now and   
      
   >again I save myself a lot of pain down the track. This is becoming more   
   and   
   >more the standard today and so I strongly advise you tone down your posts   
   -   
   >ignore those you do not like if you wish - and yes sometimes you cannot   
   help   
   >but reply - always remember in todays connected world you can be very   
   >visible.   
   >   
   >Now, if the job is not just data migration but perhaps System Replacement,   
      
   >then you will be in immediate *trouble*. The reason is that you will need   
   to   
   >be able to use Paradox For Windows extremely well because you will need   
   to   
   >locate/read/understand the OPAL code in order to replicate Business Rules   
   -   
   >perhaps even order of Data storage. Just about every Paradox application   
   is   
   >different not unlike a C++ program. Every programmer has their modus   
   >operandi and so you will need to handle that situation.   
   >   
   >Finally, in my opinion I would actually recommend *against* what they are   
      
   >trying to do. This is a backwards step technologywise and will most likely   
      
   >have severe performance issues which may be seen as a reflection upon your   
      
   >skills in MSACCESS rather than a poor development choice. You m,ight care   
   to   
   >take that approach - even if you do not get the job you would be able to   
      
   >hold your head high.   
   >   
   >Leslie.   
   >   
   >"Dominick DiMantova"  wrote in message   
   >news:48924fad$1@pnews.thedbcommunity.com...   
   >>   
   >> Well, Mike, I'm not trying to offend you, but you did give me some very   
      
   >> good   
   >> info here, but Michelle gave me the best advice yet. There were two   
   >> gentlemen   
   >> here who acted like rude a**holes and I put them in their places! No one   
   >> talks junk like that to me! Anyway, as long as I'm familiar with Paradox,   
   >> I can successfully do the job this prospective client is asking. I've   
      
   >> applied   
   >> for this project, but it's up to the client if he/she wants to grant me   
   an   
   >> interview. I'm on a scale of 9/10 in Access. But, if I'm granted an   
   >> interview,   
   >> as least I can talking intelligently about paradox to convince the client   
   >> that at LEAST I do the job, provided I'm provided with specs and stuff   
      
   >> like   
   >> that.   
   >>   
   >   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca